Triple
T30000625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidama Region |
E762156
|
entity |
| Predicate | gainedRegionalStatusBy |
P168346
|
FINISHED |
| Object | referendum |
—
|
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: referendum | Statement: [Sidama Region, gainedRegionalStatusBy, referendum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedRegionalStatusBy Context triple: [Sidama Region, gainedRegionalStatusBy, referendum]
-
A.
regionStatus
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
-
B.
statusInRegion
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
C.
statusProgramRegion
Indicates the current state or condition of a program within a specific geographic or administrative region.
-
D.
governsInRegionWithStatus
Indicates that an entity exercises governing authority within a specified region under a particular legal, political, or administrative status.
-
E.
hasSubregionStatus
Indicates that one region holds an official or defined status as a subregion within a larger geographic or administrative area.
- F. None of above. chosen
Provenance (4 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794da2cc8190af2afa95c616305a |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:41 p.m.