Triple
T22963918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Line SL4 |
E570981
|
entity |
| Predicate | isSurfaceRoute |
P150421
|
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: [Silver Line SL4, isSurfaceRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSurfaceRoute Context triple: [Silver Line SL4, isSurfaceRoute, true]
-
A.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
B.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
C.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
D.
isKeyRoute
Indicates that a route plays a primary or strategically important role within a network or system.
-
E.
isMajorRouteFor
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f66fbc8190a4a7b73d17537132 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:47 p.m.