Triple
T12820192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qusay Hussein |
E306507
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Qusay |
E306507
|
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: Qusay | Statement: [Qusay Hussein, givenName, Qusay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Qusay Context triple: [Qusay Hussein, givenName, Qusay]
-
A.
Qusay
chosen
Qusay was the second son of former Iraqi president Saddam Hussein and a key figure in his father's regime, overseeing security and military forces until his death in 2003.
-
B.
Buraimi
Buraimi is an oasis town in northeastern Oman, historically significant as a strategic frontier settlement near the UAE border.
-
C.
Khaldoon
Khaldoon is an Arabic masculine given name commonly used in the Middle East.
-
D.
Belqasim
Belqasim is a personal given name of Arabic origin, used primarily in North African and Middle Eastern cultures.
-
E.
Qahtan
Qahtan is a prominent and historically significant Arab tribal confederation traditionally associated with southern and central Arabia.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9e5a2481908921d097df541db8 |
completed | April 10, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68ed165188190a4cac781c753fb23 |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 9, 2026, 5:31 p.m.