Triple
T9444966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibrahim Tuqan |
E227740
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Tuqan |
E505606
|
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: Tuqan | Statement: [Ibrahim Tuqan, familyName, Tuqan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tuqan Context triple: [Ibrahim Tuqan, familyName, Tuqan]
-
A.
Touqan
chosen
Touqan is a family name of notable Palestinian origin, associated with prominent poets, politicians, and intellectuals in the Arab world.
-
B.
Qanjobal
Qanjobal is a Mayan language spoken primarily by the Qʼanjobʼal people in the highlands of Guatemala.
-
C.
Kuqa
Kuqa is an ancient oasis city in China’s Xinjiang region that historically served as a key Buddhist and Silk Road cultural center in the Tarim Basin.
-
D.
Qaʾan
Qaʾan is a Mongol imperial title signifying the supreme ruler of the Mongol Empire, comparable to the Great Khan.
-
E.
Khashuri
Khashuri is a town in central Georgia that serves as an important regional transport hub and gateway between eastern and western parts of the country.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f32aee88190a43573f97fa1e49d |
completed | April 1, 2026, 8:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d110669ca48190bbaf772e2e6aa457 |
completed | April 4, 2026, 1:21 p.m. |
Created at: March 30, 2026, 7:51 p.m.