Triple
T21190761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saada Governorate |
E522204
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Saada |
—
|
NE NERFINISHED |
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: Saada | Statement: [Saada Governorate, capital, Saada]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saada Context triple: [Saada Governorate, capital, Saada]
-
A.
Saada
chosen
Saada is a city and governorate in northern Yemen known as a stronghold and historical center of the Houthi movement.
-
B.
Salha
Salha is a Jordanian princess and member of the Hashemite royal family.
-
C.
Sauda
Sauda is a small industrial town and municipality in Rogaland county, Norway, known for its hydropower-based industry and dramatic fjord and mountain landscape.
-
D.
Saada city
Saada city is a historic urban center in northern Yemen known for its traditional architecture and role as a stronghold of the Houthi movement.
-
E.
Suqaylabiyah
Suqaylabiyah is a town in western Syria known for its predominantly Christian population and its location near the Orontes River in the Hama region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.