Triple
T8862339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changshou Lu Station |
E210920
|
entity |
| Predicate | hasVerticalTransport |
P35396
|
FINISHED |
| Object | escalators |
—
|
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: escalators | Statement: [Changshou Lu Station, hasVerticalTransport, escalators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerticalTransport Context triple: [Changshou Lu Station, hasVerticalTransport, escalators]
-
A.
hasGroundTransportation
Indicates that an entity provides, includes, or is connected to transportation services or options that operate on land (e.g., cars, buses, trains).
-
B.
hasLift
chosen
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
C.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
D.
hasPublicTransitFunction
Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
-
E.
hasTransportationSystem
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc610263048190931bb2c3ac573a08 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.