Triple
T10489704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheka Zone |
E247381
|
entity |
| Predicate | hasWoreda |
P847
|
FINISHED |
| Object | Masha woreda |
—
|
LITERAL 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: Masha woreda | Statement: [Sheka Zone, hasWoreda, Masha woreda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWoreda Context triple: [Sheka Zone, hasWoreda, Masha woreda]
-
A.
isRuralDistrictOf
Indicates that one administrative area is a rural district that belongs to or is governed as part of another, typically larger, administrative unit.
-
B.
hasComarca
Indicates that one entity is associated with, or belongs to, a specific comarca (an administrative or territorial district).
-
C.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
D.
hasGmina
Indicates that an entity is administratively associated with, or belongs to, a specific gmina (a basic local government unit/municipality).
-
E.
hasTown
chosen
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
- F. None of above.
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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097ca5c081908b47a08ca7885650 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.