Triple
T34837417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mudki |
E1004237
|
entity |
| Predicate | HardingeTitle |
P13335
|
FINISHED |
| Object | Governor-General of India |
—
|
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: Governor-General of India | Statement: [Battle of Mudki, HardingeTitle, Governor-General of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HardingeTitle Context triple: [Battle of Mudki, HardingeTitle, Governor-General of India]
-
A.
hadTitle
chosen
Indicates that an entity held or was assigned a specific title or formal designation.
-
B.
higherTitleOf
Indicates that one entity holds a job or position title that is hierarchically superior to the title held by another entity.
-
C.
eraTitleWith
Indicates a relationship where a specific era is associated with or designated by a particular title.
-
D.
earlyTitleOf
Indicates that one entity served as an earlier or preliminary title for another entity.
-
E.
hegemonicTitle
Indicates that an entity holds a dominant, overarching, or primary title or position of authority within a hierarchical or power-structured context.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.