Triple
T16551851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angara launch complex |
E402089
|
entity |
| Predicate | hasRailOrRoadAccess |
P124024
|
FINISHED |
| Object | rail transport for rocket stages |
—
|
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: rail transport for rocket stages | Statement: [Angara launch complex, hasRailOrRoadAccess, rail transport for rocket stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailOrRoadAccess Context triple: [Angara launch complex, hasRailOrRoadAccess, rail transport for rocket stages]
-
A.
hasRailFacility
Indicates that an entity possesses or is served by a rail-related facility, such as a railway station, terminal, or yard.
-
B.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
-
C.
connectsToRailwayNetwork
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
-
D.
railwayAccess
Indicates that an entity has direct access to, connection with, or service by a railway line or station.
-
E.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc56f9081908bb8f6433a1a688d |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.