Triple
T16153679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutuzovskaya MCC station |
E391977
|
entity |
| Predicate | isInPassengerService |
P121615
|
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: [Kutuzovskaya MCC station, isInPassengerService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPassengerService Context triple: [Kutuzovskaya MCC station, isInPassengerService, yes]
-
A.
hasPassengerOnlyService
Indicates that the service provided involves only the transportation of passengers, with no freight or cargo component.
-
B.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
C.
hasPassengerUsageCategory
Indicates the classification of how a passenger-related resource or service is used (e.g., its usage type or category for passengers).
-
D.
hasPassengerAirlineService
Indicates that a location or facility is served by scheduled passenger airline flights.
-
E.
isOnPassengerNetwork
Indicates that an entity is part of, connected to, or operates within a passenger transportation network.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e57e95c8190ae4ed641be974ce5 |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e18445155481909892b8aaa23cc159 |
completed | April 17, 2026, 12:52 a.m. |
Created at: April 10, 2026, 5:01 a.m.