Triple
T224840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haiti |
E4291
|
entity |
| Predicate | majorEarthquake |
P5296
|
FINISHED |
| Object | 2010 Haiti earthquake |
—
|
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: 2010 Haiti earthquake | Statement: [Haiti, majorEarthquake, 2010 Haiti earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorEarthquake Context triple: [Haiti, majorEarthquake, 2010 Haiti earthquake]
-
A.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
-
B.
earthquakeMagnitude
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
C.
facedMajorEarthquake
chosen
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
-
D.
majorIsland
Indicates that an island is the primary or most significant island within a specified geographic or political context.
-
E.
epicenter
Indicates the central point or focal location from which an event, influence, or effect originates or is most intensely experienced.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.