Triple
T23143638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spoornet |
E577527
|
entity |
| Predicate | ownedRailwayAssets |
P34147
|
FINISHED |
| Object | locomotives |
—
|
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: locomotives | Statement: [Spoornet, ownedRailwayAssets, locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedRailwayAssets Context triple: [Spoornet, ownedRailwayAssets, locomotives]
-
A.
ownedRollingStock
chosen
Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
-
B.
railwayOwner
Indicates that one entity owns, controls, or holds proprietary rights over a railway or railway system used by another entity.
-
C.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
D.
originalRailway
Indicates that a railway is the first or initial line from which others in a network, route, or system originate or are derived.
-
E.
railcode
Indicates that an entity is associated with a specific railway code used for identification or classification within a rail system.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecc3710819088ac5d72dad0459a |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.