Triple
T21964048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 3B |
E542410
|
entity |
| Predicate | hasGangwayType |
P90236
|
FINISHED |
| Object | inter-vehicle gangway connections |
—
|
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-vehicle gangway connections | Statement: [Mark 3B, hasGangwayType, inter-vehicle gangway connections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGangwayType Context triple: [Mark 3B, hasGangwayType, inter-vehicle gangway connections]
-
A.
hasGangway
Indicates that one entity is equipped with or connected to a gangway that provides access or passage to or from another entity.
-
B.
hasGangwayAtCabEnd
Indicates that a vehicle or unit has a gangway located at its cab end, allowing passage between connected units from that end.
-
C.
gangwayType
chosen
Indicates the specific kind or configuration of gangway used to provide passage between areas or vehicles.
-
D.
hasGatewayType
Indicates that an entity is associated with or configured to use a specific type or category of gateway.
-
E.
hasFaregates
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12459e1848190aa8d4ccc97f434b8 |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:01 p.m.