Triple
T33267330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Humanitarian Day 2012 campaign |
E851686
|
entity |
| Predicate | organizedForEvent |
P28084
|
FINISHED |
| Object | World Humanitarian Day 2012 |
—
|
NE NERFINISHED |
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: World Humanitarian Day 2012 | Statement: [World Humanitarian Day 2012 campaign, organizedForEvent, World Humanitarian Day 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedForEvent Context triple: [World Humanitarian Day 2012 campaign, organizedForEvent, World Humanitarian Day 2012]
-
A.
organisedFor
chosen
Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
-
B.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
C.
organizedDuring
Indicates that an event or activity was arranged or took place within a specified time period or temporal context.
-
D.
eventTypeOrganized
Indicates that an entity organized or arranged a specific type or category of event.
-
E.
alsoOrganized
Indicates that the same entity was additionally responsible for organizing another related event, activity, or 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:32 a.m.