Triple
T23126093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hampshire Motor Speedway |
E577032
|
entity |
| Predicate | hasBackStretchLength |
P151017
|
FINISHED |
| Object | approximately 1,500 feet |
—
|
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,500 feet | Statement: [New Hampshire Motor Speedway, hasBackStretchLength, approximately 1,500 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackStretchLength Context triple: [New Hampshire Motor Speedway, hasBackStretchLength, approximately 1,500 feet]
-
A.
hasLongStretchIn
Indicates that something extends for a considerable or continuous distance within a specified area, medium, or context.
-
B.
frontStretchLength
Indicates the measured length of the front stretch portion of something (such as a track, course, or path).
-
C.
isStretchOf
Indicates that one linear feature (such as a road, river, or path) constitutes a continuous segment or portion of another, longer linear feature.
-
D.
hasDragStripLength
Indicates the length measurement of a drag strip associated with an entity.
-
E.
hasBarLength
Indicates that an entity possesses a bar whose length is specified or measured.
- F. None of above. chosen
Provenance (4 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e5482588190b95b36075ecc7f24 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:59 p.m.