Triple
T8726279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatham Main Line |
E207138
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Sittingbourne |
E48172
|
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: Sittingbourne | Statement: [Chatham Main Line, passesThrough, Sittingbourne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sittingbourne Context triple: [Chatham Main Line, passesThrough, Sittingbourne]
-
A.
Sittingbourne
chosen
Sittingbourne is an industrial and commuter town in southeast England, located in the county of Kent.
-
B.
Sittingbourne and Sheppey
Sittingbourne and Sheppey is a UK parliamentary constituency in Kent that covers the town of Sittingbourne and the Isle of Sheppey.
-
C.
Uckfield
Uckfield is a small market town in East Sussex, England, known for its historic high street and role as a local commercial and commuter hub.
-
D.
Henham
Henham is a small rural village located in the English county of Suffolk.
-
E.
Littlebourne
Littlebourne is a village and civil parish in Kent, England, situated near the city of Canterbury.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d158b0481908249610458f97306 |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf2912c4e08190a147fc31db6788d1 |
completed | April 3, 2026, 2:42 a.m. |
Created at: March 30, 2026, 6:36 p.m.