Triple
T21937411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobalt |
E541727
|
entity |
| Predicate | secondaryHistoricalIndustry |
P3008
|
FINISHED |
| Object | cobalt 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: cobalt mining | Statement: [Cobalt, secondaryHistoricalIndustry, cobalt mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryHistoricalIndustry Context triple: [Cobalt, secondaryHistoricalIndustry, cobalt mining]
-
A.
hasSecondaryIndustry
Indicates that an entity is associated with an additional, non-primary industry in which it operates or participates.
-
B.
formerKeyIndustry
Indicates that an entity was once a primary or strategically important industry for another entity but no longer holds that status.
-
C.
modernIndustry
Indicates that an entity operates within or is characteristic of contemporary, technologically advanced industrial practices and sectors.
-
D.
hasHistoricIndustry
chosen
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
E.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1241e35bc81909eb3225d5cd97b92 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:55 p.m.