Triple
T24508456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 11 Rivalry |
E606145
|
entity |
| Predicate | participantsDistanceApart |
P7750
|
FINISHED |
| Object | approximately 10 miles |
—
|
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 10 miles | Statement: [Route 11 Rivalry, participantsDistanceApart, approximately 10 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantsDistanceApart Context triple: [Route 11 Rivalry, participantsDistanceApart, approximately 10 miles]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
formerDistance
Indicates that a distance or spatial separation between entities existed in the past but no longer holds in the present.
-
D.
isDistant
Indicates that one entity is far away or separated by a large distance from another entity.
-
E.
numberOfDistances
Indicates the count of distinct distance values associated with or measured between entities in a given context.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.