Triple
T4714459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freeway Face-Off |
E104597
|
entity |
| Predicate | distanceBetweenHomeArenasApproxKm |
P22795
|
FINISHED |
| Object | 45 |
—
|
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: 45 | Statement: [Freeway Face-Off, distanceBetweenHomeArenasApproxKm, 45]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceBetweenHomeArenasApproxKm Context triple: [Freeway Face-Off, distanceBetweenHomeArenasApproxKm, 45]
-
A.
approximateDistanceKm
chosen
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
-
B.
homeArenaOfChampionTeam
Indicates that a particular arena serves as the primary home venue for a specified champion team.
-
C.
homeArenaAlternateName
Indicates that an entity’s home arena is known by an alternate or secondary name.
-
D.
distanceToSuccessorStadium
Indicates the measured distance between a stadium and the stadium that directly succeeds it in a defined sequence or timeline.
-
E.
distance
Indicates the spatial separation or length between two points, objects, or locations.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.