Triple
T29449516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandiagara Escarpment |
E746937
|
entity |
| Predicate | previouslyInhabitedBy |
P3032
|
FINISHED |
| Object | Tellem people |
—
|
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: Tellem people | Statement: [Bandiagara Escarpment, previouslyInhabitedBy, Tellem people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyInhabitedBy Context triple: [Bandiagara Escarpment, previouslyInhabitedBy, Tellem people]
-
A.
historicallyInhabitedBy
chosen
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
B.
originalInhabitant
Indicates that an entity was among the first or earliest residents of a particular place or territory.
-
C.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
D.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
E.
inhabitedIn
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 28, 2026, 3:31 p.m.