Triple
T16344687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longford, London |
E396899
|
entity |
| Predicate | withinHeathrowPerimeter |
P123051
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Longford, London, withinHeathrowPerimeter, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinHeathrowPerimeter Context triple: [Longford, London, withinHeathrowPerimeter, no]
-
A.
distanceFromHeathrow
Indicates the measured spatial distance between a given entity and Heathrow.
-
B.
distanceToGatwickAirport
Indicates the measured distance between a given entity’s location and Gatwick Airport.
-
C.
fareZoneFromCentralLondon
Indicates the public transport fare zone in which a location lies, measured relative to central London.
-
D.
locatedInTravelcardZoneBoundary
Indicates that something lies on or within the defined boundary of a specific travelcard fare zone.
-
E.
withinLondonCommuterBelt
Indicates that a location lies within the geographic area from which people commonly commute into London for work or study.
- F. None of above. chosen
Provenance (4 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0da1808190b6477613a07c7a88 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.