Triple
T17382697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baidoa |
E422608
|
entity |
| Predicate | roadConnection |
P385
|
FINISHED |
| Object | Hudur |
E422610
|
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: Hudur | Statement: [Baidoa, roadConnection, Hudur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hudur Context triple: [Baidoa, roadConnection, Hudur]
-
A.
Hudur
chosen
Hudur is a key urban center in southwestern Somalia that serves as an administrative and commercial hub for the surrounding region.
-
B.
Agallah
Agallah is an American rapper and hip-hop producer known for his gritty East Coast sound and work with underground and mainstream artists alike.
-
C.
Taltal
Taltal is a coastal city in northern Chile known for its historic mining activity and proximity to the Atacama Desert.
-
D.
Hezir
Hezir is a biblical figure listed among the priestly families of ancient Israel, associated with the Benei Hezir priestly division.
-
E.
Khidrana
Khidrana is the former name of Muktsar, a historically significant town in Punjab, India, known for its association with Sikh history and the Battle of Muktsar.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a86d8cc81909281b22f5da87d70 |
completed | April 19, 2026, 2:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a019ff72ca08190a5ea8a1ba6330728 |
completed | May 11, 2026, 9:23 a.m. |
Created at: April 10, 2026, 5:45 a.m.