Triple
T35564147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Daytona 500 |
E1027720
|
entity |
| Predicate | announcedAttendance |
P45171
|
FINISHED |
| Object | 140000 |
—
|
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: 140000 | Statement: [2015 Daytona 500, announcedAttendance, 140000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedAttendance Context triple: [2015 Daytona 500, announcedAttendance, 140000]
-
A.
attendanceAnnounced
chosen
Indicates that an official statement has been made about whether and/or how many people will attend an event.
-
B.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another entity.
-
C.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
D.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
-
E.
announcedProgram
Indicates that an entity has publicly communicated or declared the existence or details of a particular program.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.