Triple
T10630740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altufyevo |
E250444
|
entity |
| Predicate | hasRailYardOrSidingsNearby |
P90976
|
FINISHED |
| Object | turnback sidings north of the station |
—
|
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: turnback sidings north of the station | Statement: [Altufyevo, hasRailYardOrSidingsNearby, turnback sidings north of the station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailYardOrSidingsNearby Context triple: [Altufyevo, hasRailYardOrSidingsNearby, turnback sidings north of the station]
-
A.
hasRailYard
Indicates that one entity possesses, contains, or includes a rail yard as part of its facilities or infrastructure.
-
B.
hasNearbyRailway
Indicates that one entity is located close to a railway associated with or relevant to another entity.
-
C.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
D.
hasTurnbackSidings
chosen
Indicates that a railway line, route, or station includes sidings specifically used for turning back or reversing trains.
-
E.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df93a2b88190a0f3a52b8e88f54f |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:01 p.m.