Triple
T34702298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randal Tyson Track Center |
E1000406
|
entity |
| Predicate | hasStraightaway |
P121550
|
FINISHED |
| Object | 60-meter straightaway |
—
|
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: 60-meter straightaway | Statement: [Randal Tyson Track Center, hasStraightaway, 60-meter straightaway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStraightaway Context triple: [Randal Tyson Track Center, hasStraightaway, 60-meter straightaway]
-
A.
hasStraightCourse
Indicates that something follows a direct, uncurved path or progression without significant deviation.
-
B.
hasStartFinishStraight
Indicates that something includes a straight segment that serves as both the starting and finishing section of a course or track.
-
C.
hasMainStraight
chosen
Indicates that an entity (such as a race track or road) includes a primary, central straight section used as its main straightaway.
-
D.
isMostlyStraight
Indicates that an entity is predominantly but not entirely straight in orientation, alignment, or form.
-
E.
hasStraightLines
Indicates that the related entity possesses or is characterized by straight, non-curved lines.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
Created at: May 3, 2026, 3:59 p.m.