Triple
T2579894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose rock |
E57062
|
entity |
| Predicate | associatedWithMineral |
P28979
|
FINISHED |
| Object | gypsum |
—
|
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: gypsum | Statement: [Rose rock, associatedWithMineral, gypsum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMineral Context triple: [Rose rock, associatedWithMineral, gypsum]
-
A.
hasImportantMineral
chosen
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
-
B.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
C.
mineralizationType
Indicates the specific kind or style of mineral deposition or ore-forming process characterizing a mineralized occurrence or deposit.
-
D.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
E.
mineralogy
Indicates the study or characterization of the mineral composition and properties associated with an 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a9fd3c8190a521931e40cd801c |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.