Triple
T4201583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Tōhoku earthquake and tsunami |
E86077
|
entity |
| Predicate | tsunamiMaximumHeight |
P34012
|
FINISHED |
| Object | about 40.5 metres |
—
|
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: about 40.5 metres | Statement: [2011 Tōhoku earthquake and tsunami, tsunamiMaximumHeight, about 40.5 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiMaximumHeight Context triple: [2011 Tōhoku earthquake and tsunami, tsunamiMaximumHeight, about 40.5 metres]
-
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.
tsunamiType
Indicates the specific classification or category of a tsunami associated with an event or location.
-
D.
hasTsunamiRisk
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
-
E.
producedTsunami
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af037da30481908106b27a88d59140 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.