Triple
T11909009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central London Railway |
E283344
|
entity |
| Predicate | initialRoute |
P50277
|
FINISHED |
| Object | Shepherd's Bush to Bank |
—
|
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: Shepherd's Bush to Bank | Statement: [Central London Railway, initialRoute, Shepherd's Bush to Bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialRoute Context triple: [Central London Railway, initialRoute, Shepherd's Bush to Bank]
-
A.
firstRoutes
Indicates that one route or path is the initial or primary route taken or assigned among a set of possible routes.
-
B.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
C.
originalRoute
Indicates that one route is the initial or primary path from which another route is derived, modified, or compared.
-
D.
earlyRoute
Indicates that a route or path is taken or scheduled earlier than a standard, expected, or alternative route.
-
E.
initialScheduledRoute
chosen
Indicates that an entity is assigned to follow a specific route as originally planned or scheduled, before any changes or updates.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.