Triple
T30795660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labé Region |
E784221
|
entity |
| Predicate | partOfHighlandSystem |
P165213
|
FINISHED |
| Object | Fouta Djallon highlands |
—
|
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: Fouta Djallon highlands | Statement: [Labé Region, partOfHighlandSystem, Fouta Djallon highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfHighlandSystem Context triple: [Labé Region, partOfHighlandSystem, Fouta Djallon highlands]
-
A.
isHighlandLandmarkFor
Indicates that a landmark is recognized as a notable or defining feature specifically within a highland area or region.
-
B.
isInHighlandRegion
chosen
Indicates that an entity is located within a highland or elevated geographic region.
-
C.
mountainSystem
Indicates a relationship where multiple mountains are grouped together as part of the same connected or coherent mountain system or range.
-
D.
isPartOfHighestMassifOf
Indicates that one entity is a constituent part or subfeature of the highest massif within a given geographic or topographic context.
-
E.
isHighlandConstituency
Indicates that a given constituency is located within or classified as part of the Highland region.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: April 29, 2026, 8:42 p.m.