Triple
T24252591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DBAG Class 484 |
E603570
|
entity |
| Predicate | hasLowFloorSections |
P66651
|
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: [DBAG Class 484, hasLowFloorSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowFloorSections Context triple: [DBAG Class 484, hasLowFloorSections, yes]
-
A.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
-
B.
hasFloorElevation
Indicates that one entity has a specified vertical height or level above a reference point (such as sea level or ground) for its floor.
-
C.
lowFloor
chosen
Indicates that something has a floor positioned close to ground level, allowing easy, step-free access.
-
D.
hasEntranceElevation
Indicates the elevation at which an entity’s entrance is located, typically measured relative to a reference level such as sea level or ground level.
-
E.
hasLowSeatHeight
Indicates that an entity’s seat is positioned at a relatively low height compared to a typical or reference standard.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8aff788190bb37fc8ab04bde00 |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.