Triple
T37350258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labrador Trough |
E927300
|
entity |
| Predicate | containsCommodity |
P193582
|
FINISHED |
| Object | iron ore |
—
|
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 | Statement: [Labrador Trough, containsCommodity, iron ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCommodity Context triple: [Labrador Trough, containsCommodity, iron ore]
-
A.
hasKeyCommodity
chosen
Indicates that an entity possesses or is associated with a primary or strategically important commodity.
-
B.
supportsCommodity
Indicates that one entity provides the necessary functionality, infrastructure, or compatibility for another entity to handle, use, or trade a specified commodity.
-
C.
mentionsCommodity
Indicates that one entity refers to, cites, or brings up a particular commodity in some form of content or communication.
-
D.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
E.
supportedCommodity
Indicates that an entity provides backing, assistance, or endorsement for a particular commodity.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a019579463c8190b51e39183b57bbaf |
completed | May 11, 2026, 8:38 a.m. |
| PD | Predicate disambiguation | batch_6a0192d309488190a3d86c93e7138c77 |
completed | May 11, 2026, 8:26 a.m. |
Created at: May 3, 2026, 4:16 p.m.