Triple
T9431001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquamarine |
E227373
|
entity |
| Predicate | belongsToMineralGroup |
P34461
|
FINISHED |
| Object | silicate minerals |
—
|
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: silicate minerals | Statement: [Aquamarine, belongsToMineralGroup, silicate minerals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToMineralGroup Context triple: [Aquamarine, belongsToMineralGroup, silicate minerals]
-
A.
mineralGroup
chosen
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
B.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
C.
hasImportantMineral
Indicates that an entity contains or is associated with a mineral considered significant or valuable in a given context.
-
D.
mineralizationType
Indicates the specific kind or style of mineral deposition or ore-forming process characterizing a mineralized occurrence or deposit.
-
E.
belongsToBreedGroup
Indicates that an animal is classified as a member of a specific breed group.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.