Triple
T1140337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier Voyager family |
E23434
|
entity |
| Predicate | hasGangway |
P26478
|
FINISHED |
| Object | inter-coach gangways |
—
|
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: inter-coach gangways | Statement: [Bombardier Voyager family, hasGangway, inter-coach gangways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGangway Context triple: [Bombardier Voyager family, hasGangway, inter-coach gangways]
-
A.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
B.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
C.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
D.
hasFaregates
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
-
E.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bddfa598819088690e1ab010ba0b |
completed | March 1, 2026, 10:29 p.m. |
Created at: March 1, 2026, 7:44 p.m.