Triple
T31873121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sretensky Bulvar |
E813662
|
entity |
| Predicate | hasTransferCorridorType |
P86994
|
FINISHED |
| Object | underground pedestrian passage |
—
|
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: underground pedestrian passage | Statement: [Sretensky Bulvar, hasTransferCorridorType, underground pedestrian passage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransferCorridorType Context triple: [Sretensky Bulvar, hasTransferCorridorType, underground pedestrian passage]
-
A.
haveCrossBorderCorridor
Indicates that there exists a designated corridor or route enabling movement or interaction across a national or regional border between the related entities.
-
B.
transferCorridor
chosen
Indicates a relationship where something moves or is passed from one side or entity to another through an intermediate passage or channel.
-
C.
isGatewayCorridorFor
Indicates that something serves as a primary access route or passageway enabling movement or connection to another place, system, or area.
-
D.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
E.
hasParallelCorridorRole
Indicates that one entity serves in a corridor-related role that is parallel or equivalent to the corridor role of another entity.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: April 30, 2026, 11:55 p.m.