Triple
T6253242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TW postcode area |
E140097
|
entity |
| Predicate | coversTown |
P847
|
FINISHED |
| Object | Hanworth |
E473440
|
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: Hanworth | Statement: [TW postcode area, coversTown, Hanworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanworth Context triple: [TW postcode area, coversTown, Hanworth]
-
A.
Hanworth
chosen
Hanworth is a suburban residential area in west London, England, known for its parks, local amenities, and proximity to Heathrow Airport.
-
B.
Hanau
Hanau is a town in the German state of Hesse, known as an important regional center and the birthplace of the Brothers Grimm.
-
C.
Backworth
Backworth is a village in North Tyneside, England, historically associated with coal mining and now largely residential.
-
D.
Herford
Herford is a historic town in northwestern Germany known for its medieval architecture and location in the region of North Rhine-Westphalia.
-
E.
Hagen
Hagen is a city in the Ruhr region of North Rhine-Westphalia in western Germany, known historically as an industrial and transport hub.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063417c8c8190945049881819d307 |
completed | March 22, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c2442a556081908b91e7d999a82514 |
completed | March 24, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:24 p.m.