Triple
T13480233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Up Country |
E318352
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Hatton |
E460404
|
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: Hatton | Statement: [Up Country, hasTown, Hatton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hatton Context triple: [Up Country, hasTown, Hatton]
-
A.
Hatton
Hatton is a small suburban area in West London, England, situated near Heathrow Airport and within the London Borough of Hounslow.
-
B.
Hatton
Hatton is an English surname historically associated with several notable figures in British political and social life.
-
C.
Hatton
chosen
Hatton is a town in Sri Lanka’s hill country known as a gateway to tea plantations and the pilgrimage site of Adam’s Peak.
-
D.
Hatton
Hatton is a village and civil parish in South Derbyshire, England, known historically for its railway connections and local industry.
-
E.
Hattonrigg
Hattonrigg is a residential area forming part of the town of Bellshill in North Lanarkshire, Scotland.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf36c6b08190ba99400600e0b662 |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75481b6f48190b6cd6cef3e8dee20 |
completed | May 3, 2026, 1:58 p.m. |
Created at: April 9, 2026, 9:42 p.m.