Triple
T25782212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Central Kitchen |
E649319
|
entity |
| Predicate | notableResponseTo |
P767
|
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: [World Central Kitchen, notableResponseTo, 2010 Haiti earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableResponseTo Context triple: [World Central Kitchen, notableResponseTo, 2010 Haiti earthquake]
-
A.
hasNotableResponse
Indicates that an entity has received a significant, noteworthy, or widely recognized reaction or feedback in response to it.
-
B.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
C.
wasResponseTo
chosen
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
-
D.
notableReception
Indicates that something has received significant attention, recognition, or response from audiences, critics, or the public.
-
E.
notableLetter
Indicates that a letter associated with an entity is especially significant, famous, or otherwise noteworthy in relation to that entity.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 22, 2026, 5:51 a.m.