Triple
T9520803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morganite |
E229637
|
entity |
| Predicate | occurrenceEnvironment |
P76824
|
FINISHED |
| Object | granite pegmatites |
—
|
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: granite pegmatites | Statement: [Morganite, occurrenceEnvironment, granite pegmatites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurrenceEnvironment Context triple: [Morganite, occurrenceEnvironment, granite pegmatites]
-
A.
ecoregion
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
-
B.
secondaryEnvironment
Indicates that an entity is associated with an additional or supporting environment distinct from its primary one.
-
C.
ecozone
Indicates that two entities stand in a biogeographical relationship where one is an ecological zone (ecozone) that characterizes or contains the other.
-
D.
preferredHabitat
chosen
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
E.
dominantEnvironment
Indicates the primary or prevailing environment or setting in which an entity most characteristically exists, operates, or exerts influence.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9884dd5c8190b69c178cb2ac75c2 |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:59 p.m.