Triple
T14725793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Stoke |
E345935
|
entity |
| Predicate | hasAmenity |
P105
|
FINISHED |
| Object | Little Stoke Park |
E345935
|
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: Little Stoke Park | Statement: [Little Stoke, hasAmenity, Little Stoke Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Little Stoke Park Context triple: [Little Stoke, hasAmenity, Little Stoke Park]
-
A.
Stoke Park
Stoke Park is a large public park in Guildford, Surrey, known for its open green spaces, sports facilities, and community events.
-
B.
Stoke Park
Stoke Park is a historic country estate in Buckinghamshire, England, known for its stately home, landscaped parkland, and luxury golf and leisure facilities.
-
C.
Stoke Park
Stoke Park is a residential suburb and parkland area of Ipswich in Suffolk, England.
-
D.
Little Stoke
chosen
Little Stoke is a suburban village in South Gloucestershire, England, situated near Bristol and known primarily as a residential community.
-
E.
Redlees Park
Redlees Park is a public green space in Isleworth, Middlesex, England, offering recreational facilities and natural areas for local residents and visitors.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec26013c8819090512f8b4df9cc87 |
completed | April 14, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf099eaf48190b89032b6ac769e67 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 10, 2026, 1:29 a.m.