Triple
T30167153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilsland railway station |
E766825
|
entity |
| Predicate | lineConnects |
P105759
|
FINISHED |
| Object | Newcastle upon Tyne |
—
|
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: Newcastle upon Tyne | Statement: [Gilsland railway station, lineConnects, Newcastle upon Tyne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineConnects Context triple: [Gilsland railway station, lineConnects, Newcastle upon Tyne]
-
A.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
B.
networkLine
Indicates that there is a connection or linkage between entities within a network structure or system.
-
C.
connectsCitiesViaLine
chosen
Indicates a relationship where a transportation line directly links two or more cities.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f083c208190aa0ead76cb6ced98 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:23 p.m.