Triple
T33053816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Independence Day Reception |
E845797
|
entity |
| Predicate | attendeesInclude |
P33356
|
FINISHED |
| Object | politicians |
—
|
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: politicians | Statement: [Presidential Independence Day Reception, attendeesInclude, politicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendeesInclude Context triple: [Presidential Independence Day Reception, attendeesInclude, politicians]
-
A.
eventParticipant
chosen
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
B.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
C.
customaryAttendee
Indicates that an entity habitually or traditionally attends a particular event, gathering, or type of occasion.
-
D.
invitedParticipant
Indicates that an entity has been invited to take part in an event, activity, or interaction.
-
E.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.