Triple
T26352412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Underground S8 Stock |
E662936
|
entity |
| Predicate | walkThroughGangways |
P26478
|
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: [London Underground S8 Stock, walkThroughGangways, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkThroughGangways Context triple: [London Underground S8 Stock, walkThroughGangways, yes]
-
A.
hasGangway
chosen
Indicates that one entity is equipped with or connected to a gangway that provides access or passage to or from another entity.
-
B.
walkThrough
Indicates moving through or along the interior or extent of something, typically traversing a space or environment from one side or point to another.
-
C.
gangwayType
Indicates the specific kind or configuration of gangway used to provide passage between areas or vehicles.
-
D.
hasGangwayAtCabEnd
Indicates that a vehicle or unit has a gangway located at its cab end, allowing passage between connected units from that end.
-
E.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fece7d881909ef602630bd8da89 |
completed | May 2, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:46 p.m.