Triple
T1964026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khan Noonien Singh |
E42647
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Khan |
E64995
|
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: Khan | Statement: [Khan Noonien Singh, title, Khan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khan Context triple: [Khan Noonien Singh, title, Khan]
-
A.
Khan
chosen
Khan is a common surname of Central and South Asian origin historically associated with nobility and leadership, now widely used across Muslim and other communities worldwide.
-
B.
Kahn
Kahn is a surname most famously associated with Louis Kahn, the influential 20th-century architect known for his monumental and timeless modernist buildings.
-
C.
Salim
Salim was the birth name of Jahangir, the fourth Mughal emperor of India known for his patronage of the arts and consolidation of the empire.
-
D.
Malik
Malik is a common Arabic surname and given name used across various cultures, often meaning "king" or "owner."
-
E.
Khan of Khans
"Khan of Khans" is an exalted imperial title historically used to denote a supreme ruler above other khans, signifying paramount sovereignty and authority.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3ada4148190ad830d4a3d7fd662 |
completed | March 7, 2026, 5:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adfbd32eb88190a2069b6490b12e5d |
completed | March 8, 2026, 10:44 p.m. |
Created at: March 4, 2026, 7:36 p.m.