Triple
T8892351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kintbury railway station |
E211709
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Kintbury |
E211709
|
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: Kintbury | Statement: [Kintbury railway station, serves, Kintbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kintbury Context triple: [Kintbury railway station, serves, Kintbury]
-
A.
Kintbury
chosen
Kintbury is a rural village in Berkshire, England, known for its picturesque countryside setting and historic charm.
-
B.
Hawkenbury
Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
-
C.
Carbury
Carbury is a fictional English surname most notably associated with characters in Anthony Trollope’s novel "The Way We Live Now."
-
D.
Buntingford
Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
-
E.
Heytesbury
Heytesbury is a historic village and former parliamentary borough in Wiltshire, England.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61bb46c881909e579bb1926e5204 |
completed | April 1, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba1e46a48190b7a559f9d9bd348d |
completed | April 3, 2026, 1:01 p.m. |
Created at: March 30, 2026, 6:54 p.m.