Triple
T26065182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Speedway |
E657380
|
entity |
| Predicate | trackLengthKilometers |
P69216
|
FINISHED |
| Object | approximately 1.4 km |
—
|
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: approximately 1.4 km | Statement: [Iowa Speedway, trackLengthKilometers, approximately 1.4 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackLengthKilometers Context triple: [Iowa Speedway, trackLengthKilometers, approximately 1.4 km]
-
A.
trackLengthApproxKm
chosen
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
B.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
C.
trackLengthMiles
Indicates the length of a track measured in miles.
-
D.
tourDistanceApproxKm
Indicates an approximate total distance, measured in kilometers, covered during a tour or journey.
-
E.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60696110c8190b48e3769a5836657 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:22 p.m.