Triple
T4201585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Tōhoku earthquake and tsunami |
E86077
|
entity |
| Predicate | tsunamiArrivalTime |
P54338
|
FINISHED |
| Object | within minutes on the Tōhoku coast |
—
|
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: within minutes on the Tōhoku coast | Statement: [2011 Tōhoku earthquake and tsunami, tsunamiArrivalTime, within minutes on the Tōhoku coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiArrivalTime Context triple: [2011 Tōhoku earthquake and tsunami, tsunamiArrivalTime, within minutes on the Tōhoku coast]
-
A.
tsunamiArrivalTimeInLisbon
Indicates the specific time at which a tsunami reaches or is expected to reach Lisbon.
-
B.
tsunamiTravelTimeToEastAfrica
Indicates the amount of time it takes for a tsunami to travel from its source to reach the coasts of East Africa.
-
C.
tsunamiTravelTimeToSriLanka
Indicates the amount of time it takes for a tsunami to travel from its origin to reach Sri Lanka.
-
D.
tsunamiAffectedArea
Indicates that a given area has been impacted or damaged by a tsunami.
-
E.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69af02e4e2308190b527e3b78eb8fa71 |
completed | March 9, 2026, 5:27 p.m. |
Created at: March 9, 2026, 3:49 p.m.