Triple
T10886374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Metro 81-767 series |
E257055
|
entity |
| Predicate | hasGangwayConnection |
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: [Moscow Metro 81-767 series, hasGangwayConnection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGangwayConnection Context triple: [Moscow Metro 81-767 series, hasGangwayConnection, 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.
hasFareGateConnectionTo
Indicates that there is a direct passage or connection between two areas that is controlled or mediated by fare gates.
-
C.
hasFaregates
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
-
D.
hasCausewayConnection
Indicates a relationship where two locations are physically linked by a causeway, allowing passage between them.
-
E.
gangwayType
Indicates the specific kind or configuration of gangway used to provide passage between areas or vehicles.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dea1a88190b916879be8d74413 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.