Triple
T7212546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadler GTW DMU |
E149440
|
entity |
| Predicate | doorLevel |
P75466
|
FINISHED |
| Object | low‑floor access at platforms |
—
|
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: low‑floor access at platforms | Statement: [Stadler GTW DMU, doorLevel, low‑floor access at platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorLevel Context triple: [Stadler GTW DMU, doorLevel, low‑floor access at platforms]
-
A.
doorType
Indicates the specific kind or category of door associated with an entity.
-
B.
doorConfiguration
Indicates how a door is arranged or set up in relation to its frame, opening direction, and operational characteristics.
-
C.
gateType
Indicates the specific kind or classification of a gate associated with an entity.
-
D.
floorAccess
Indicates that an entity is permitted to enter or use a specific floor or level within a building or structure.
-
E.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e98b61448190add3624a818fdc7b |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:53 p.m.