Triple
T16820841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coca-Cola 600 |
E408884
|
entity |
| Predicate | fanAttendanceType |
P24594
|
FINISHED |
| Object | in-person spectators |
—
|
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: in-person spectators | Statement: [Coca-Cola 600, fanAttendanceType, in-person spectators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanAttendanceType Context triple: [Coca-Cola 600, fanAttendanceType, in-person spectators]
-
A.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
B.
spectatorType
chosen
Indicates the role or category of a spectator in relation to an event or activity.
-
C.
fanExperienceFeature
Indicates a feature or aspect specifically designed to shape, enhance, or characterize a fan’s overall experience.
-
D.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
E.
fanInvolved
Indicates that a fan actively participates in or is directly involved with a particular event, activity, or interaction.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e6b59c8190ad562a80e71ce54c |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.