Triple
T29656610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas–Ramsey line (via St John’s) |
E750284
|
entity |
| Predicate | northernTownServed |
P104901
|
FINISHED |
| Object | Ramsey |
—
|
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: Ramsey | Statement: [Douglas–Ramsey line (via St John’s), northernTownServed, Ramsey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernTownServed Context triple: [Douglas–Ramsey line (via St John’s), northernTownServed, Ramsey]
-
A.
northernTownConnected
Indicates that a town located in the northern region is connected (e.g., by roads, transport, or infrastructure) to another place.
-
B.
townServed
chosen
Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
-
C.
servesAreaNorthOf
Indicates that an entity provides services or coverage to an area located geographically north of a specified reference area.
-
D.
northernTerminusMunicipality
Indicates that a municipality serves as the northern endpoint or terminus of a route, line, or similar linear feature.
-
E.
northernTerminusCity
Indicates that one city serves as the northern endpoint or final stop of a route, line, or corridor relative to another location.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:55 p.m.