Triple
T28003959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford–Luton rivalry |
E707222
|
entity |
| Predicate | distanceBetweenTownsMiles |
P45616
|
FINISHED |
| Object | approximately 19 |
—
|
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 19 | Statement: [Watford–Luton rivalry, distanceBetweenTownsMiles, approximately 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceBetweenTownsMiles Context triple: [Watford–Luton rivalry, distanceBetweenTownsMiles, approximately 19]
-
A.
distanceBetweenHomeCities
Indicates the measured spatial distance separating the home cities of two entities.
-
B.
approximateGreatCircleDistanceMiles
chosen
Indicates the approximate distance, measured in miles, between two locations along the great-circle path on the surface of a sphere (typically the Earth).
-
C.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
D.
distanceFromTacoma (miles)
Indicates the physical distance, measured in miles, between an entity’s location and the city of Tacoma.
-
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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: April 27, 2026, 7:59 p.m.