Triple
T35599242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheshire Lines main line |
E1028721
|
entity |
| Predicate | sectionInUse |
P3120
|
FINISHED |
| Object | Liverpool to Warrington section |
—
|
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: Liverpool to Warrington section | Statement: [Cheshire Lines main line, sectionInUse, Liverpool to Warrington section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionInUse Context triple: [Cheshire Lines main line, sectionInUse, Liverpool to Warrington section]
-
A.
usesSectionOf
Indicates that one entity makes use of a specific section or part of another entity.
-
B.
sectionProvided
Indicates that a specific section or portion of content has been supplied or made available by one entity to another.
-
C.
operatorInSection
Indicates that an operator is assigned to, works within, or is responsible for a specific section.
-
D.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
E.
guardedSectionOf
Indicates a relationship where one entity serves as a protective or security boundary for a specific section or portion of another entity.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.