Triple
T6921883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir |
E160204
|
entity |
| Predicate | relatedTitle |
P914
|
FINISHED |
| Object | Amir |
E66146
|
NE 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: Amir | Statement: [Mir, relatedTitle, Amir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amir Context triple: [Mir, relatedTitle, Amir]
-
A.
Amir
chosen
Amir is a noble and military title historically used across the Islamic world, often denoting a commander, prince, or high-ranking leader.
-
B.
Amir
Amir is the conflicted Afghan protagonist of "The Kite Runner," whose journey is defined by childhood betrayal, guilt, and a quest for redemption.
-
C.
Sohrab
Sohrab is a tragic hero in the Persian epic Shahnameh, famed as the valiant but ill-fated son of the champion Rostam.
-
D.
Paul Amir
Paul Amir is a philanthropist and art patron known for his major support of cultural and architectural projects, including the Herta and Paul Amir Building.
-
E.
Abdul
Abdul is a common male given name of Arabic origin meaning "servant of" (typically followed by one of the names of God).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fb8ac48190b50bbc47fad8288f |
completed | March 27, 2026, 7:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c75137dd848190b35ff72725f886ba |
completed | March 28, 2026, 3:55 a.m. |
Created at: March 27, 2026, 2:26 p.m.