Triple
T17296284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wembley Park |
E419918
|
entity |
| Predicate | locatedInTravelDirectionCorridor |
P126862
|
FINISHED |
| Object | northwest of central London |
—
|
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: northwest of central London | Statement: [Wembley Park, locatedInTravelDirectionCorridor, northwest of central London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTravelDirectionCorridor Context triple: [Wembley Park, locatedInTravelDirectionCorridor, northwest of central London]
-
A.
locatedInTransportCorridor
Indicates that an entity is situated within a designated transport corridor used for the movement of people or goods.
-
B.
isMostHeavilyTraveledCorridorIn
Indicates that a particular route or corridor experiences the highest volume of travel or traffic within a specified area or region.
-
C.
isInTravelDirection
Indicates that one entity lies along or matches the direction in which another entity is traveling or moving.
-
D.
followedCorridor
Indicates that an entity moved along and stayed within the path of a corridor from one point to another.
-
E.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e437881d688190a633beacba6bc0ae |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.