Triple
T3176721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alivardi Khan |
E66481
|
entity |
| Predicate | officeAcquiredBy |
P43556
|
FINISHED |
| Object | coup against Sarfaraz Khan |
—
|
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: coup against Sarfaraz Khan | Statement: [Alivardi Khan, officeAcquiredBy, coup against Sarfaraz Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeAcquiredBy Context triple: [Alivardi Khan, officeAcquiredBy, coup against Sarfaraz Khan]
-
A.
acquiredCompany
Indicates that one entity has purchased and taken ownership or control of another company.
-
B.
officeSucceededBy
chosen
Indicates that one office or position is followed or replaced by another office or position in a succession sequence.
-
C.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
D.
officeMergedInto
Indicates that one office has been combined with and absorbed into another office, ceasing to exist as a separate entity.
-
E.
acquisitionAnnouncedBy
Indicates that an acquisition event was publicly announced by the specified announcing entity (such as a company or organization).
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69b0bec8190957913b44d876079 |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.