Triple
T36073269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leavine Family Racing |
E1043422
|
entity |
| Predicate | bestRaceFinishEvent |
P87460
|
FINISHED |
| Object | 2019 Bass Pro Shops NRA Night Race at Bristol |
—
|
NE NERFINISHED |
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: 2019 Bass Pro Shops NRA Night Race at Bristol | Statement: [Leavine Family Racing, bestRaceFinishEvent, 2019 Bass Pro Shops NRA Night Race at Bristol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestRaceFinishEvent Context triple: [Leavine Family Racing, bestRaceFinishEvent, 2019 Bass Pro Shops NRA Night Race at Bristol]
-
A.
bestRaceFinish
Indicates the highest (best) finishing position an entity has achieved in a race.
-
B.
raceWon
Indicates that one participant has achieved victory in a race or competitive event over others.
-
C.
sportsEventFinish
chosen
Indicates the outcome or completion status of a sports event, typically linking the event to its final result or placement of participants.
-
D.
raceTypeWon
Indicates the specific type or category of race that an entity has won.
-
E.
raceWins
Indicates that one participant wins or finishes ahead of another in a race or competitive event.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.