Triple
T10568842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasfi al-Tal |
E249424
|
entity |
| Predicate | birthPlace |
P1
|
FINISHED |
| Object | Irbid |
E87274
|
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: Irbid | Statement: [Wasfi al-Tal, birthPlace, Irbid]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Irbid Context triple: [Wasfi al-Tal, birthPlace, Irbid]
-
A.
Irbid
chosen
Irbid is a large city in northern Jordan known as an important economic, educational, and cultural center.
-
B.
Irbid Governorate
Irbid Governorate is a populous administrative region in northern Jordan known for its agricultural productivity and the major city of Irbid as its capital.
-
C.
Amman
Amman is the capital and largest city of Jordan, serving as a major political, economic, and cultural center in the Arab world.
-
D.
Ma’an
Ma’an is a major city in southern Jordan that serves as an important regional hub and gateway to nearby desert and archaeological sites.
-
E.
Mafraq
Mafraq is a city in northern Jordan that serves as a strategic transport hub and gateway to the Syrian border and surrounding desert regions.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5272ff53c8190ae7c399d49b585f5 |
completed | April 7, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94b4c26ec8190910efdf4a236d654 |
completed | April 10, 2026, 7:11 p.m. |
Created at: April 6, 2026, 12:37 p.m.