Triple
T24521719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Inaugural Committee 2009 |
E606547
|
entity |
| Predicate | eventPlanned |
P35067
|
FINISHED |
| Object | first inauguration of Barack Obama |
—
|
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: first inauguration of Barack Obama | Statement: [Presidential Inaugural Committee 2009, eventPlanned, first inauguration of Barack Obama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventPlanned Context triple: [Presidential Inaugural Committee 2009, eventPlanned, first inauguration of Barack Obama]
-
A.
eventManagement
Indicates the organization, coordination, and oversight of all activities and resources involved in planning and executing an event.
-
B.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
C.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
D.
organisedEvent
chosen
Indicates that an entity planned, coordinated, and carried out an event.
-
E.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.