Triple
T28694222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antamina copper-zinc deposit |
E729367
|
entity |
| Predicate | alterationStyle |
P82242
|
FINISHED |
| Object | skarn alteration |
—
|
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: skarn alteration | Statement: [Antamina copper-zinc deposit, alterationStyle, skarn alteration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alterationStyle Context triple: [Antamina copper-zinc deposit, alterationStyle, skarn alteration]
-
A.
alterationStyles
chosen
Indicates the styles, methods, or types of modifications or alterations applied to an entity.
-
B.
alterationType
Indicates the specific kind or category of change or modification that has been applied to an entity or relationship.
-
C.
adaptationStyle
Indicates how an entity adjusts or modifies its behavior, form, or strategy in response to changing conditions or influences.
-
D.
stylingTool
Indicates a tool or instrument used to style, shape, or arrange something (typically hair, clothing, or design elements).
-
E.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 5:38 a.m.