Triple
T1057791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porter (MBTA station) |
E22835
|
entity |
| Predicate | hasVerticalCirculation |
P1532
|
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: [Porter (MBTA station), hasVerticalCirculation, escalators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerticalCirculation Context triple: [Porter (MBTA station), hasVerticalCirculation, escalators]
-
A.
hasElevators
Indicates that one entity is equipped with or contains one or more elevators for vertical transportation.
-
B.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
C.
hasBalustrades
Indicates that one entity features or is equipped with balustrades as part of its structure or design.
-
D.
hasEscalators
chosen
Indicates that one entity is equipped with or contains escalators that can be used for movement between different levels or areas.
-
E.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.