Triple
T26153809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Thameslink network |
E659900
|
entity |
| Predicate | coreSectionBetween |
P134795
|
FINISHED |
| Object | St Pancras International |
—
|
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: St Pancras International | Statement: [London Thameslink network, coreSectionBetween, St Pancras International]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreSectionBetween Context triple: [London Thameslink network, coreSectionBetween, St Pancras International]
-
A.
isSectionBetween
chosen
Indicates that one section lies between two other specified sections within an ordered structure or sequence.
-
B.
linedSections
Indicates that one section is arranged or positioned in alignment with another section.
-
C.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
-
D.
guardedSectionOf
Indicates a relationship where one entity serves as a protective or security boundary for a specific section or portion of another entity.
-
E.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c0d35288190b016726366d3ad27 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:26 p.m.