Triple
T28313245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pikes Peak granite |
E714058
|
entity |
| Predicate | commonMineral |
P45236
|
FINISHED |
| Object | quartz |
—
|
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: quartz | Statement: [Pikes Peak granite, commonMineral, quartz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMineral Context triple: [Pikes Peak granite, commonMineral, quartz]
-
A.
hasMineral
chosen
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
B.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
C.
typeOfMineralsCovered
Indicates that one entity specifies or lists the kinds or categories of minerals that are included, addressed, or affected by another entity.
-
D.
typeOfMineralProduced
Indicates that a specified mineral is produced or extracted as a result of a particular process, operation, or source.
-
E.
mineralFamily
Indicates that one mineral belongs to, or is classified within, the broader family or group represented by another mineral or mineral category.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 27, 2026, 11:41 p.m.