Triple
T876848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1755 Lisbon earthquake |
E18935
|
entity |
| Predicate | tsunamiArrivalTimeInLisbon |
P20998
|
FINISHED |
| Object | about 20–40 minutes after the main shock |
—
|
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 20–40 minutes after the main shock | Statement: [1755 Lisbon earthquake, tsunamiArrivalTimeInLisbon, about 20–40 minutes after the main shock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiArrivalTimeInLisbon Context triple: [1755 Lisbon earthquake, tsunamiArrivalTimeInLisbon, about 20–40 minutes after the main shock]
-
A.
earthquakeLocalTime
Indicates the local time at which an earthquake event occurred at its specific location.
-
B.
earthquakeDate
Indicates the specific calendar date on which an earthquake event occurred.
-
C.
earthquakeMagnitude
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
D.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
-
E.
landfallLocation
Indicates the geographic location where a storm or similar weather system first makes landfall.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acaf30a48190a10ed7fee464c444 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:39 p.m.