Triple
T19065020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Tātua-a-Riukiuta |
E466630
|
entity |
| Predicate | geologicalField |
P96002
|
FINISHED |
| Object | volcanology |
—
|
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: volcanology | Statement: [Te Tātua-a-Riukiuta, geologicalField, volcanology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalField Context triple: [Te Tātua-a-Riukiuta, geologicalField, volcanology]
-
A.
geologicalStudyField
chosen
Indicates that a particular field or area is the subject or location of a geological study or investigation.
-
B.
geologyRelatedTo
Indicates a relationship where one geological entity, feature, or concept is connected, associated, or relevant to another within the domain of geology.
-
C.
geologicalRole
Indicates the functional or classificatory role an entity plays within geological processes, structures, or contexts.
-
D.
geologyIncludes
Indicates that one geological entity contains, encompasses, or has as a component another geological entity.
-
E.
geologicalSystem
Indicates that one entity is a geological system (e.g., rock units, structures, or processes forming a coherent geologic framework) associated with or characterizing the other entity.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19799d8819099d0b848771ae425 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.