Triple
T35330355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldora Speedway |
E1020298
|
entity |
| Predicate | hasInfieldPitArea |
P50635
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Eldora Speedway, hasInfieldPitArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfieldPitArea Context triple: [Eldora Speedway, hasInfieldPitArea, yes]
-
A.
hasPit
Indicates that one entity possesses, contains, or is characterized by a pit or hollow space.
-
B.
hasInfield
chosen
Indicates that an entity possesses or includes a designated infield area, typically within a larger spatial or structural context.
-
C.
hasInfieldStands
Indicates that spectator stands or seating areas are located within the infield area of a sports venue.
-
D.
infieldSurface
Indicates that one entity serves as the playing surface material or type for the infield area of another entity (such as a sports field or stadium).
-
E.
hasPitLane
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0061454944819088a0babfe60f69fc |
completed | May 10, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_6a0060b9ee108190b91e8d99a16f2b30 |
completed | May 10, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:03 p.m.