Triple
T37344357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newmont Mining |
E927130
|
entity |
| Predicate | hasKeyResourceType |
P3729
|
FINISHED |
| Object | open-pit mines |
—
|
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: open-pit mines | Statement: [Newmont Mining, hasKeyResourceType, open-pit mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyResourceType Context triple: [Newmont Mining, hasKeyResourceType, open-pit mines]
-
A.
hasKeyResource
Indicates that an entity possesses or depends on a critical resource necessary for its function, operation, or success.
-
B.
hasKeyAssetType
Indicates that an entity possesses or is associated with a specific type or category of key (primary or critical) asset.
-
C.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
D.
hasTypeOfResource
chosen
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
E.
hasKeyTextType
Indicates that something is associated with a primary or defining type of textual content used as its key or main text.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:16 p.m.