Triple
T28694224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antamina copper-zinc deposit |
E729367
|
entity |
| Predicate | associatedIntrusionType |
P203607
|
FINISHED |
| Object | granodiorite |
—
|
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: granodiorite | Statement: [Antamina copper-zinc deposit, associatedIntrusionType, granodiorite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedIntrusionType Context triple: [Antamina copper-zinc deposit, associatedIntrusionType, granodiorite]
-
A.
associatedDamType
Indicates that there is a specific type or classification of dam linked or related to the referenced entity.
-
B.
relatedAttack
Indicates that one attack is connected or associated with another attack, such as being part of the same incident, campaign, or sequence of actions.
-
C.
trapType
Indicates the specific kind or category of trap associated with an entity or situation.
-
D.
systemThreatType
Indicates the category or nature of threat that a system poses or is exposed to.
-
E.
threatTypeEncountered
Indicates that an entity has come across or experienced a specific type of threat.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a01b31b233c819091974a06f7a76d4a |
completed | May 11, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_6a01b2c147008190bbf9e0fa1bbae1f3 |
completed | May 11, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_6a01b31a5b408190abde68df45a82c81 |
completed | May 11, 2026, 10:44 a.m. |
Created at: April 28, 2026, 5:38 a.m.