Triple
T32537847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitby–Pickering line |
E831637
|
entity |
| Predicate | sectionsReusedBy |
P95595
|
FINISHED |
| Object | North Yorkshire Moors Railway |
—
|
NE NERFINISHED |
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: North Yorkshire Moors Railway | Statement: [Whitby–Pickering line, sectionsReusedBy, North Yorkshire Moors Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionsReusedBy Context triple: [Whitby–Pickering line, sectionsReusedBy, North Yorkshire Moors Railway]
-
A.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
-
B.
sideUsedBy
Indicates that a particular side or aspect of something is utilized or employed by a specified entity.
-
C.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
D.
sharesSectionsWith
Indicates that two entities have one or more sections or segments in common.
-
E.
partiallyReusedAs
chosen
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c579194c819096d249335b3ccf6d |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:01 a.m.