Triple
T37688653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Purandar (1665) |
E938441
|
entity |
| Predicate | fortsCededCount |
P118898
|
FINISHED |
| Object | 23 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 23 | Statement: [Treaty of Purandar (1665), fortsCededCount, 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortsCededCount Context triple: [Treaty of Purandar (1665), fortsCededCount, 23]
-
A.
numberOfForts
chosen
Indicates the count of forts associated with a given entity or context.
-
B.
wasCededAfter
Indicates that control or ownership of one entity was formally transferred to another entity following a specified event or point in time.
-
C.
surrenderedIn
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
-
D.
countrySurrendering
Indicates that one country formally yields to another country’s authority or control, typically ending a conflict or war.
-
E.
garrisonSurrenderedTo
Indicates that a defending military garrison formally capitulated and yielded control to another party.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.