Triple
T4115408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Taupō |
E90277
|
entity |
| Predicate | isTectonicallyActive |
P22035
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lake Taupō, isTectonicallyActive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTectonicallyActive Context triple: [Lake Taupō, isTectonicallyActive, true]
-
A.
hasGeologicalActivity
chosen
Indicates that an entity exhibits or is associated with ongoing or past geological processes such as volcanism, tectonics, or seismic activity.
-
B.
tectonicActivityCharacteristic
Indicates a characteristic or property that describes the nature, intensity, or pattern of tectonic activity associated with something.
-
C.
locatedOnTectonicPlate
Indicates that one entity (typically a geographic region or feature) lies upon or is situated on the tectonic plate represented by the other entity.
-
D.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
-
E.
hasTectonicSetting
Indicates the geological or tectonic environment in which an entity (such as a rock unit, region, or event) is situated or formed.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.