Triple
T23255335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maidstone East Line |
E581852
|
entity |
| Predicate | servesTown |
P847
|
FINISHED |
| Object |
Hollingbourne
Hollingbourne is a village in Kent, England, situated near Maidstone and the North Downs.
|
E1577003
|
NE FINISHED |
How this triple was built (4 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: Hollingbourne | Statement: [Maidstone East Line, servesTown, Hollingbourne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hollingbourne Context triple: [Maidstone East Line, servesTown, Hollingbourne]
-
A.
Speldhurst
Speldhurst is a rural village and civil parish in Kent, England, known for its historic church, traditional pubs, and scenic countryside near Royal Tunbridge Wells.
-
B.
Sellindge
Sellindge is a rural village in Kent, England, situated between Ashford and Folkestone and known for its community amenities and surrounding countryside.
-
C.
Northbourne
Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
-
D.
Northbourne
Northbourne is a residential suburb within the coastal urban area of Bournemouth in Dorset, England.
-
E.
Oldbourne
Oldbourne is an alternative historical spelling of "Old Bourne," typically referring to an old stream or settlement whose name incorporates the term "bourne" for a small river.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Hollingbourne Triple: [Maidstone East Line, servesTown, Hollingbourne]
Generated description
Hollingbourne is a village in Kent, England, situated near Maidstone and the North Downs.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Hollingbourne Target entity description: Hollingbourne is a village in Kent, England, situated near Maidstone and the North Downs.
-
A.
Speldhurst
Speldhurst is a rural village and civil parish in Kent, England, known for its historic church, traditional pubs, and scenic countryside near Royal Tunbridge Wells.
-
B.
Sellindge
Sellindge is a rural village in Kent, England, situated between Ashford and Folkestone and known for its community amenities and surrounding countryside.
-
C.
Northbourne
Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
-
D.
Northbourne
Northbourne is a residential suburb within the coastal urban area of Bournemouth in Dorset, England.
-
E.
Oldbourne
Oldbourne is an alternative historical spelling of "Old Bourne," typically referring to an old stream or settlement whose name incorporates the term "bourne" for a small river.
- F. None of above. chosen
Provenance (5 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193fadac881908579b5729718ee41 |
completed | April 29, 2026, 5:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c3f6a050c81908242087190a5a42e |
completed | May 19, 2026, 10:46 a.m. |
| NEDg | Description generation | batch_6a0c40297d3c8190b366b60cec3dbbf8 |
completed | May 19, 2026, 10:49 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0c40ffd67481908931ffc2d91fb02b |
completed | May 19, 2026, 10:52 a.m. |
Created at: April 17, 2026, 4:11 p.m.