Triple
T31212064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxenholme (historical shorter form) |
E795771
|
entity |
| Predicate | usedInRailNetwork |
P95666
|
FINISHED |
| Object | British railway network |
—
|
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: British railway network | Statement: [Oxenholme (historical shorter form), usedInRailNetwork, British railway network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRailNetwork Context triple: [Oxenholme (historical shorter form), usedInRailNetwork, British railway network]
-
A.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
B.
connectsToRailwayNetwork
chosen
Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
-
C.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
D.
appliesToRailwayNetwork
Indicates that something is relevant or specifically applicable to a railway network as a whole.
-
E.
usedByRailroad
Indicates that something is utilized or operated by a railroad or railway company.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 29, 2026, 9:09 p.m.