Triple
T25712173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fen Line between Cambridge and King's Lynn |
E644761
|
entity |
| Predicate | connectsToAt |
P167776
|
FINISHED |
| Object | Ely–Peterborough 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: Ely–Peterborough line | Statement: [Fen Line between Cambridge and King's Lynn, connectsToAt, Ely–Peterborough line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToAt Context triple: [Fen Line between Cambridge and King's Lynn, connectsToAt, Ely–Peterborough line]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
C.
connectsTerminus
Indicates that one entity serves as a terminus that is directly linked or joined to another entity.
-
D.
terminusConnectsTo
chosen
Indicates that a transportation route’s endpoint is directly linked or transitions to another route, line, or terminal.
-
E.
connectsToBusAt
Indicates that one entity has an access or transfer point where it links to a bus service at a specific location or stop.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 21, 2026, 9:17 p.m.