Triple
T35124006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purandhar Fort |
E1014244
|
entity |
| Predicate | treatyRepresentativeMughal |
P37762
|
FINISHED |
| Object | Jai Singh I |
—
|
NE NERFINISHED |
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: Jai Singh I | Statement: [Purandhar Fort, treatyRepresentativeMughal, Jai Singh I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyRepresentativeMughal Context triple: [Purandhar Fort, treatyRepresentativeMughal, Jai Singh I]
-
A.
successorAsMughalAlly
Indicates that one entity becomes the next political or military ally of the Mughal power, taking over that allied role from another entity.
-
B.
combatantRulerMughals
Indicates a ruler associated with the Mughal Empire who participated as a combatant in a specific conflict or battle.
-
C.
commanderForDelhiSultanate
Indicates that a person served as a military commander on behalf of the Delhi Sultanate.
-
D.
treatySignedFor
chosen
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
E.
signatoryMinister
Indicates that a minister has formally signed or endorsed a document, agreement, or treaty as an official signatory.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.