Triple
T3533817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagapattinam |
E74721
|
entity |
| Predicate | tsunamiImpact |
P46843
|
FINISHED |
| Object | severe damage in 2004 Indian Ocean tsunami |
—
|
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: severe damage in 2004 Indian Ocean tsunami | Statement: [Nagapattinam, tsunamiImpact, severe damage in 2004 Indian Ocean tsunami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiImpact Context triple: [Nagapattinam, tsunamiImpact, severe damage in 2004 Indian Ocean tsunami]
-
A.
tsunamiAffectedArea
chosen
Indicates that a given area has been impacted or damaged by a tsunami.
-
B.
producedTsunami
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
-
C.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
-
D.
tsunamiType
Indicates the specific classification or category of a tsunami associated with an event or location.
-
E.
hasTsunamiRisk
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9b945481909867d44b810e8b1f |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.