Triple
T798425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O’Higgins Region |
E17072
|
entity |
| Predicate | hasMiningActivity |
P19172
|
FINISHED |
| Object | copper mining |
—
|
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: copper mining | Statement: [O’Higgins Region, hasMiningActivity, copper mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningActivity Context triple: [O’Higgins Region, hasMiningActivity, copper mining]
-
A.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
B.
miningActivityEnd
Indicates the point in time or event at which a mining operation or activity ceases or is formally concluded.
-
C.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
D.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
E.
minedSince
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b4d9548190aad5fdf1211cf8cd |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
| PDg | Predicate description generation | batch_69a4a5bed20c81909ecc28bf42594e72 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:38 p.m.