Triple
T7999818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thame |
E186216
|
entity |
| Predicate | parliamentaryConstituency |
P2710
|
FINISHED |
| Object | Henley |
E37009
|
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: [Thame, parliamentaryConstituency, Henley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henley Context triple: [Thame, parliamentaryConstituency, Henley]
-
A.
Henley
Henley is a small village and civil parish located in the county of Suffolk in eastern England.
-
B.
Bray
Bray is a picturesque village on the River Thames in Berkshire, England, noted for its historic charm and renowned fine-dining restaurants.
-
C.
Henley-on-Thames
chosen
Henley-on-Thames is a historic English riverside town in Oxfordshire, best known for hosting the annual Henley Royal Regatta on the River Thames.
-
D.
Windsor
Windsor is a town in Norfolk, England, served by a station on the Sandringham railway line.
-
E.
Windsor
Windsor is a village in south-central Wisconsin, United States, located just north of the city of Madison.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c9b67988190a8a4a2c960017400 |
completed | March 31, 2026, 3:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe114372c819086f06e184d5ebde2 |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 5:17 p.m.