Triple
T36691511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | allanite-(Ce) |
E905967
|
entity |
| Predicate | occursInGeologicalSetting |
P19734
|
FINISHED |
| Object | felsic igneous rocks |
—
|
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: felsic igneous rocks | Statement: [allanite-(Ce), occursInGeologicalSetting, felsic igneous rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInGeologicalSetting Context triple: [allanite-(Ce), occursInGeologicalSetting, felsic igneous rocks]
-
A.
foundInGeologicSetting
chosen
Indicates that something occurs, is present, or has been discovered within a particular geological environment or context.
-
B.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
-
C.
hasGeologicalNature
Indicates that something possesses a specific geological character, composition, or formation type.
-
D.
hasGeologicalSignificance
Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
-
E.
geologicalRole
Indicates the functional or classificatory role an entity plays within geological processes, structures, or contexts.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:12 p.m.