Triple
T6372595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemble |
E143386
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Thames Head |
E37608
|
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: Thames Head | Statement: [Kemble, near, Thames Head]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thames Head Context triple: [Kemble, near, Thames Head]
-
A.
Thames Head
chosen
Thames Head is the traditionally recognized spring in Gloucestershire, England, regarded as the starting point of the River Thames.
-
B.
Tottenham Lock
Tottenham Lock is a canal lock on the River Lea in North London, used to manage water levels and enable boat navigation along the river.
-
C.
Bablock Hythe
Bablock Hythe is a historic riverside hamlet and former ferry crossing point on the River Thames in Oxfordshire, England.
-
D.
Hythe
Hythe is a small village in northwestern Alberta, Canada, situated west of the city of Grande Prairie.
-
E.
Hythe
Hythe is a historic coastal town in Kent, England, known as one of the original Cinque Ports that once played a key role in maritime defense and trade.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06829d76c819092b476631459233a |
completed | March 22, 2026, 10:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c62d9203988190a535b4f06f478292 |
completed | March 27, 2026, 7:11 a.m. |
Created at: March 22, 2026, 4:33 p.m.