Triple
T34169144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Eritrea |
E876495
|
entity |
| Predicate | partOfEcologicalZone |
P948
|
FINISHED |
| Object | Afar Triangle |
—
|
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: Afar Triangle | Statement: [Southern Eritrea, partOfEcologicalZone, Afar Triangle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfEcologicalZone Context triple: [Southern Eritrea, partOfEcologicalZone, Afar Triangle]
-
A.
isEcologicalZone
Indicates that one entity functions as, or is classified as, an ecological zone in relation to another entity.
-
B.
ecoregion
chosen
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
-
C.
ecozone
Indicates that two entities stand in a biogeographical relationship where one is an ecological zone (ecozone) that characterizes or contains the other.
-
D.
hasEcologicalZones
Indicates that an entity is associated with, contains, or is characterized by one or more distinct ecological zones.
-
E.
ecoregionCode
Indicates the specific ecological region identifier associated with an entity, linking it to a defined environmental or biogeographic zone.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: May 1, 2026, 1:54 a.m.