Triple
T13149368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exeter to Plymouth line |
E312423
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | Exeter |
E122858
|
NE FINISHED |
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: Exeter | Statement: [Exeter to Plymouth line, connectsCity, Exeter]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Exeter Context triple: [Exeter to Plymouth line, connectsCity, Exeter]
-
A.
Exeter
Exeter is a historic town in Rockingham County, New Hampshire, known for its colonial heritage and as the home of the prestigious Phillips Exeter Academy.
-
B.
Exeter
chosen
Exeter is a historic cathedral city in Devon, England, known for its medieval architecture and role as a regional administrative and cultural center.
-
C.
Exeter
Exeter is a small borough in Luzerne County, Pennsylvania, situated in the Wyoming Valley near the Susquehanna River.
-
D.
Exeter
Exeter is a small town located in Otsego County in central New York State, known for its rural character and agricultural landscape.
-
E.
Bristol
Bristol is a city in central Connecticut known for being the home of ESPN and for its historic clock-making industry.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98bd1fc408190b4b5ca973bcee403 |
completed | April 10, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f72660f8d48190b437a57f2a75f6ae |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:11 p.m.