Triple
T13616342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henley, Suffolk |
E325320
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Henley |
E325320
|
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: Henley | Statement: [Henley, Suffolk, hasName, Henley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henley Context triple: [Henley, Suffolk, hasName, Henley]
-
A.
Henley
Henley is a small, affluent waterfront suburb on Sydney’s lower north shore, known for its scenic views of the Parramatta River and proximity to the city.
-
B.
Henley
chosen
Henley is a small village and civil parish located in the county of Suffolk in eastern England.
-
C.
Bray
Bray is a coastal town and popular seaside resort in eastern Ireland known for its promenade, beach, and proximity to Dublin.
-
D.
Bray
Bray is a picturesque village on the River Thames in Berkshire, England, noted for its historic charm and renowned fine-dining restaurants.
-
E.
Henley-on-Thames
Henley-on-Thames is a historic English riverside town in Oxfordshire, best known for hosting the annual Henley Royal Regatta on the River Thames.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0ad0a7c81909c7972187202db96 |
completed | April 12, 2026, 2:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f9ecc2881909f71d71e056f9459 |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:50 p.m.