Triple
T28531548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K |
E722054
|
entity |
| Predicate | isRailTransitRoute |
P30511
|
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: [K, isRailTransitRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRailTransitRoute Context triple: [K, isRailTransitRoute, true]
-
A.
isPublicTransportRoute
chosen
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
B.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
C.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
D.
isSuburbanRailway
Indicates that a railway line, service, or system operates primarily within and around a metropolitan area, typically connecting the city center with its suburbs.
-
E.
isPassengerRail
Indicates that something functions as or is classified as a passenger rail service or system, primarily used to transport people rather than freight.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 3:29 a.m.