Triple
T29522086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BR Eastern Region |
E748963
|
entity |
| Predicate | mainLineIncludes |
P88054
|
FINISHED |
| Object | East Coast Main Line |
—
|
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: East Coast Main Line | Statement: [BR Eastern Region, mainLineIncludes, East Coast Main Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLineIncludes Context triple: [BR Eastern Region, mainLineIncludes, East Coast Main Line]
-
A.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
B.
lineIncludes
chosen
Indicates that a specific line (such as a text line, code line, or route segment) contains or encompasses a given element or component.
-
C.
servesMainLine
Indicates that one entity functions as the primary or main service line for another entity.
-
D.
programIncluded
Indicates that a particular program is contained within, or forms part of, another specified collection, package, or set of programs.
-
E.
inscriptionIncludesLine
Indicates that an inscription contains a specific line of text as one of its components.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 4:42 p.m.