Triple
T12789047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagpur kingdom |
E305707
|
entity |
| Predicate | dateOfTreatyOfDeogaon |
P23330
|
FINISHED |
| Object | 1803 |
—
|
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: 1803 | Statement: [Nagpur kingdom, dateOfTreatyOfDeogaon, 1803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfTreatyOfDeogaon Context triple: [Nagpur kingdom, dateOfTreatyOfDeogaon, 1803]
-
A.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
B.
treatySignedYear
chosen
Indicates the calendar year in which a specific treaty was formally signed.
-
C.
treatyConcludedAfter
Indicates that one treaty was formally concluded at a later time than another specified treaty.
-
D.
dateSignedTreatyOfGeorgievsk
Indicates that the subject entity signed the Treaty of Georgievsk on the specified date.
-
E.
foundingTreatySignedAt
Indicates that the founding treaty establishing an entity was formally signed at a specific location.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6a61f48190972e241e70bc392c |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.