Triple
T12732396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Island Gardens DLR station |
E304272
|
entity |
| Predicate | hasPassengerLifts |
P1531
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Island Gardens DLR station, hasPassengerLifts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerLifts Context triple: [Island Gardens DLR station, hasPassengerLifts, yes]
-
A.
hasElevators
chosen
Indicates that one entity is equipped with or contains one or more elevators for vertical transportation.
-
B.
hasEscalators
Indicates that one entity is equipped with or contains escalators that can be used for movement between different levels or areas.
-
C.
hasPanoramicElevators
Indicates that an entity is equipped with elevators that provide wide, panoramic views, typically through extensive glass or open designs.
-
D.
hasHighSpeedElevators
Indicates that a building or structure is equipped with elevators capable of operating at high speeds.
-
E.
hasElevatorConnection
Indicates that there is a direct elevator-based connection or access route between two locations or entities.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.