Triple
T17372489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churnet Valley Line |
E422351
|
entity |
| Predicate | partlyOperatedAs |
P50841
|
FINISHED |
| Object | heritage railway |
—
|
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: heritage railway | Statement: [Churnet Valley Line, partlyOperatedAs, heritage railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlyOperatedAs Context triple: [Churnet Valley Line, partlyOperatedAs, heritage railway]
-
A.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
B.
operatedPortionsOf
chosen
Indicates that an agent has performed operational control or management over specific parts or segments of a larger system, asset, or entity.
-
C.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
D.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
E.
partlyServedBy
Indicates that an entity is only partially provided, covered, or supported by another entity, rather than being fully served by it.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a69d93c81908ce2d909857a3a11 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.