Triple
T26278339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowen’s reaction series |
E660634
|
entity |
| Predicate | includesMineral |
P45236
|
FINISHED |
| Object | olivine |
—
|
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: olivine | Statement: [Bowen’s reaction series, includesMineral, olivine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMineral Context triple: [Bowen’s reaction series, includesMineral, olivine]
-
A.
hasMineral
chosen
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
B.
hasMineralClass
Indicates that an entity is associated with, or categorized under, a particular mineral classification.
-
C.
isAssociatedWithMineral
Indicates that there is a relationship or connection between an entity and a specific mineral, such as composition, presence, or relevance.
-
D.
isMineralRich
Indicates that a location or substance contains a high concentration or abundance of minerals.
-
E.
hasImportantMineral
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 26, 2026, 9:58 p.m.