Triple
T16186224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 360 Knoxville Nationals |
E392809
|
entity |
| Predicate | primaryVenueUse |
P106649
|
FINISHED |
| Object | sprint car racing |
—
|
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: sprint car racing | Statement: [360 Knoxville Nationals, primaryVenueUse, sprint car racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVenueUse Context triple: [360 Knoxville Nationals, primaryVenueUse, sprint car racing]
-
A.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
B.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
C.
primaryUseArea
chosen
Indicates the main functional area or domain in which an entity is primarily used or applied.
-
D.
primaryCurrentUse
Indicates the main way something is currently being used or its principal present function.
-
E.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22061f47481909ededd5eed40f5a4 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.