Triple
T16260142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etosha Pan |
E394731
|
entity |
| Predicate | wildlifeSupported |
P46327
|
FINISHED |
| Object | elephants |
—
|
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: elephants | Statement: [Etosha Pan, wildlifeSupported, elephants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wildlifeSupported Context triple: [Etosha Pan, wildlifeSupported, elephants]
-
A.
supportsWildlife
chosen
Indicates that one entity provides conditions, resources, or protection that help sustain or benefit wildlife associated with another entity.
-
B.
supportsBirdlife
Indicates that one entity provides conditions or resources that help sustain or benefit bird life associated with another entity.
-
C.
hasWildlifeUse
Indicates that something is used by or provides a functional role for wildlife, such as habitat, food, shelter, or other ecological benefits.
-
D.
hasWildlifeStatus
Indicates the conservation or protection status assigned to wildlife associated with an entity.
-
E.
hasWildlifeHabitats
Indicates that an entity contains or supports natural environments where wildlife species live, feed, or reproduce.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c3e5388190942b0237ab5d1f0f |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.