Triple
T27420974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Bete Abba Libanos |
E693041
|
entity |
| Predicate | locatedInWoreda |
P103735
|
FINISHED |
| Object | Lasta Woreda |
—
|
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: Lasta Woreda | Statement: [Church of Bete Abba Libanos, locatedInWoreda, Lasta Woreda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInWoreda Context triple: [Church of Bete Abba Libanos, locatedInWoreda, Lasta Woreda]
-
A.
capitalOfWoreda
Indicates that one location serves as the administrative capital or main town of a specific woreda (district).
-
B.
locatedInCityWard
Indicates that one entity is situated within the administrative boundaries of a specific city ward.
-
C.
isLocatedInGovernorate
Indicates that an entity is situated within the administrative area of a specific governorate.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
isLocatedInSubdivision
chosen
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: April 27, 2026, 12:36 p.m.