Triple
T2084414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haiti After the Earthquake |
E45315
|
entity |
| Predicate | timePeriodEvent |
P35710
|
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 After the Earthquake, timePeriodEvent, 2010 Haiti earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodEvent Context triple: [Haiti After the Earthquake, timePeriodEvent, 2010 Haiti earthquake]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
C.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
D.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
E.
timePeriodImplied
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba524b60819089a11957ce6dbc4b |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:41 p.m.