Triple
T36631117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EH10 |
E904317
|
entity |
| Predicate | hasApproximateDistanceToCityCentre |
P1299
|
FINISHED |
| Object | about 2–4 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: about 2–4 miles | Statement: [EH10, hasApproximateDistanceToCityCentre, about 2–4 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDistanceToCityCentre Context triple: [EH10, hasApproximateDistanceToCityCentre, about 2–4 miles]
-
A.
hasCoordinateInCityCentreApprox
Indicates that an entity’s location is approximately within the central area of a city, based on its geographic coordinates.
-
B.
isFartherFromCityCenterThan
Indicates that one location is at a greater distance from the city center than another location.
-
C.
roadDistanceToCityCentre_km
Indicates the distance in kilometers from a location to the city centre when traveling by road.
-
D.
administrativeCenterDistance
Indicates the distance between an entity and the administrative center that governs or represents it.
-
E.
distanceFromDowntown
chosen
Indicates the physical distance between a given location and the central downtown area.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.