Triple
T8353380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean porphyry copper belt |
E196615
|
entity |
| Predicate | oreMineralogy |
P45236
|
FINISHED |
| Object | chalcopyrite |
—
|
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: chalcopyrite | Statement: [Andean porphyry copper belt, oreMineralogy, chalcopyrite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oreMineralogy Context triple: [Andean porphyry copper belt, oreMineralogy, chalcopyrite]
-
A.
mineralogy
Indicates the study or characterization of the mineral composition and properties associated with an entity.
-
B.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
C.
lithology
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
D.
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.
-
E.
hasMineral
chosen
Indicates that one entity contains, includes, or is composed of a specified mineral.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804756088190a766e1a486ccfdff |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.