Triple
T21571105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Nimba |
E532283
|
entity |
| Predicate | hasLandUseConflict |
P141795
|
FINISHED |
| Object | conservation versus iron ore mining |
—
|
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: conservation versus iron ore mining | Statement: [Mount Nimba, hasLandUseConflict, conservation versus iron ore mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandUseConflict Context triple: [Mount Nimba, hasLandUseConflict, conservation versus iron ore mining]
-
A.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
B.
landUseIssues
chosen
Indicates conflicts, problems, or concerns arising from how land is used, managed, or designated.
-
C.
hasLandUsePressure
Indicates that an area or entity is subject to demands or stresses from human or other uses of land that may affect its condition or availability.
-
D.
addressesConflictWithin
Indicates that one entity deals with, manages, or resolves a conflict that exists inside another entity or within its internal scope.
-
E.
conflictUse
Indicates a relationship where one entity’s use, application, or operation is incompatible with, obstructs, or negatively interferes with another entity’s use.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cc5c448190887a836f577d01ba |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.