Triple
T37220751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Road |
E922872
|
entity |
| Predicate | servedCentralLondon |
P48857
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Portland Road, servedCentralLondon, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedCentralLondon Context triple: [Portland Road, servedCentralLondon, true]
-
A.
servesCentralLondon
chosen
Indicates that something provides service or access specifically to the Central London area.
-
B.
toCentralLondonVia
Indicates that something (such as a route, service, or connection) leads or travels to Central London by way of a specified path, mode, or intermediary location.
-
C.
hasTerminusInCentralLondon
Indicates that the route, service, or line ends at a terminal point located within Central London.
-
D.
secondaryLondonTerminal
Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
-
E.
inLondonTravelZone
Indicates that an entity is located within one of the defined public transport fare zones of London.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: May 3, 2026, 4:15 p.m.