Triple
T8716868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 Nias–Simeulue earthquake |
E206916
|
entity |
| Predicate | tsunamiHeightApproximate |
P34012
|
FINISHED |
| Object | up to several meters locally |
—
|
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: up to several meters locally | Statement: [2005 Nias–Simeulue earthquake, tsunamiHeightApproximate, up to several meters locally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiHeightApproximate Context triple: [2005 Nias–Simeulue earthquake, tsunamiHeightApproximate, up to several meters locally]
-
A.
maximumTsunamiHeight
chosen
Indicates the greatest recorded or expected vertical height reached by a tsunami at a given location or event.
-
B.
maximumTsunamiHeightLocation
Indicates the location at which the tsunami reaches its maximum recorded or predicted height.
-
C.
tsunamiArrivalTime
Indicates the specific time at which a tsunami reaches a given location.
-
D.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
-
E.
tsunamiType
Indicates the specific classification or category of a tsunami associated with an event or location.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd9c2a08190a65ab0ce573153d2 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.