Triple
T8390520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimba County |
E197930
|
entity |
| Predicate | gainedProminenceFor |
P81954
|
FINISHED |
| Object | iron ore exports |
—
|
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: iron ore exports | Statement: [Nimba County, gainedProminenceFor, iron ore exports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedProminenceFor Context triple: [Nimba County, gainedProminenceFor, iron ore exports]
-
A.
helpedPropelToMainstreamFame
Indicates that one entity significantly contributed to another entity’s rise to widespread public recognition or mainstream popularity.
-
B.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
C.
inceptionOfNotoriety
Indicates the point or event at which an entity first becomes widely known or gains significant public notoriety.
-
D.
moreProminentSince
Indicates that one entity has become more prominent or noticeable relative to another entity starting from a specified point in time.
-
E.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
- F. None of above. chosen
Provenance (4 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb810c5c5c81908e124c64911c4e6c |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:03 p.m.