Triple
T5605059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurentia |
E147212
|
entity |
| Predicate | mineralResources |
P2856
|
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: [Laurentia, mineralResources, iron ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineralResources Context triple: [Laurentia, mineralResources, iron ore]
-
A.
economicGeology
Indicates a relationship where geological features, materials, or processes are studied or evaluated in terms of their economic value, such as for resource exploration, extraction, or utilization.
-
B.
naturalResources
chosen
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
-
C.
hasImportantMineral
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
-
D.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
E.
eraOfMajorMiningActivity
Indicates the time period during which significant or primary mining operations took place for the associated 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fa4b0881909fdbb8ea38eeb5e3 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.