Triple
T19061416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vossloh Citylink |
E466540
|
entity |
| Predicate | hasFloorHeight |
P55992
|
FINISHED |
| Object | low-floor over most of vehicle length |
—
|
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 over most of vehicle length | Statement: [Vossloh Citylink, hasFloorHeight, low-floor over most of vehicle length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloorHeight Context triple: [Vossloh Citylink, hasFloorHeight, low-floor over most of vehicle length]
-
A.
floorHeight
chosen
Indicates the vertical elevation or level at which a particular floor is positioned within a structure.
-
B.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
C.
ceilingHeight
Indicates the vertical distance from the floor to the ceiling in a given space.
-
D.
hasFloorFeature
Indicates that a floor possesses or includes a specific feature or characteristic.
-
E.
hasFloorArea
Indicates that an entity possesses a specified amount of floor space as a measurable area.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e194c854819085a0a48d22c5cebd |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.