Triple
T8018955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Smith Dinner |
E186689
|
entity |
| Predicate | hasNotableAttendees |
P10756
|
FINISHED |
| Object | U.S. presidential candidates |
—
|
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: U.S. presidential candidates | Statement: [Al Smith Dinner, hasNotableAttendees, U.S. presidential candidates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAttendees Context triple: [Al Smith Dinner, hasNotableAttendees, U.S. presidential candidates]
-
A.
hasNotableGuest
chosen
Indicates that an entity has a guest who is distinguished, prominent, or otherwise noteworthy in some significant way.
-
B.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
C.
notablePresence
Indicates that an entity has a significant or prominent presence in relation to another entity, context, or domain.
-
D.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
E.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df626e8819098a9f8908dfdad3b |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.