Triple
T26437189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayan Obo rare earth mine |
E664981
|
entity |
| Predicate | initialCommodity |
P76326
|
FINISHED |
| Object | iron |
—
|
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 | Statement: [Bayan Obo rare earth mine, initialCommodity, iron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialCommodity Context triple: [Bayan Obo rare earth mine, initialCommodity, iron]
-
A.
commodity
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
B.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
C.
otherCommodity
Indicates that an entity is associated with a commodity that is different from a primary, specified, or expected commodity in the given context.
-
D.
commodityProduced
chosen
Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
-
E.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 11:54 p.m.