Triple
T8353385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean porphyry copper belt |
E196615
|
entity |
| Predicate | alterationStyles |
P82242
|
FINISHED |
| Object | potassic 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: potassic alteration | Statement: [Andean porphyry copper belt, alterationStyles, potassic alteration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alterationStyles Context triple: [Andean porphyry copper belt, alterationStyles, potassic alteration]
-
A.
stylingTool
Indicates a tool or instrument used to style, shape, or arrange something (typically hair, clothing, or design elements).
-
B.
adaptationStyle
Indicates how an entity adjusts or modifies its behavior, form, or strategy in response to changing conditions or influences.
-
C.
stylingEnables
Indicates that one entity provides or activates styling capabilities or visual formatting for another entity.
-
D.
editingStyle
Indicates the characteristic manner or approach used when revising, arranging, or refining content.
-
E.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804756088190a766e1a486ccfdff |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:59 p.m.