Triple
T9244667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aljustrel |
E222158
|
entity |
| Predicate | hasMiningResource |
P64308
|
FINISHED |
| Object | copper |
—
|
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 | Statement: [Aljustrel, hasMiningResource, copper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiningResource Context triple: [Aljustrel, hasMiningResource, copper]
-
A.
hasMiningCommodity
chosen
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
-
B.
hasGeologicResource
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
C.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
D.
hasResourcePotential
Indicates that an entity possesses the capacity or suitability to provide, generate, or support a particular resource in the future.
-
E.
hasMiningArea
Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take place.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cd03efaa748190973916bd790f6e3a |
completed | April 1, 2026, 11:39 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.