Triple
T8353280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Pelambres mine |
E196613
|
entity |
| Predicate | oreReserveType |
P50114
|
FINISHED |
| Object | proven and probable reserves |
—
|
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: proven and probable reserves | Statement: [Los Pelambres mine, oreReserveType, proven and probable reserves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oreReserveType Context triple: [Los Pelambres mine, oreReserveType, proven and probable reserves]
-
A.
typeOfReserve
chosen
Indicates that one entity is classified as a specific kind or category of reserve in relation to another entity.
-
B.
oreType
Indicates the specific kind or classification of ore associated with an entity.
-
C.
mainReserve
Indicates that one entity serves as the primary or main reserve resource, backup, or store for another entity.
-
D.
reservationProvision
Indicates that one entity provides, allocates, or sets aside a reservation (such as a booked resource, service slot, or capacity) for another entity.
-
E.
associatedReserve
Indicates a relationship where one entity is linked to or connected with a specific reserve (such as a backup, reserve fund, or reserved resource) designated for its use or support.
- 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.