Triple
T19714593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanworth |
E473440
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Hampton |
E107671
|
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: Hampton | Statement: [Hanworth, near, Hampton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hampton Context triple: [Hanworth, near, Hampton]
-
A.
Hampton
chosen
Hampton is a suburban town in the London Borough of Richmond upon Thames, England, situated on the north bank of the River Thames.
-
B.
Hampton
Hampton is an independent coastal city in southeastern Virginia known for its historic role in early American settlement and its location at the entrance to the Chesapeake Bay.
-
C.
Hampton
Hampton is a historic coastal town in southeastern New Hampshire, known as one of the colony’s earliest settlements and now a popular beach community.
-
D.
Hampton
Hampton is a surname of English origin borne by various notable individuals, including those in the arts and public life.
-
E.
Hampton
Hampton is a suburban railway station in Melbourne, Australia, serving the bayside suburb of Hampton on the city’s Sandringham line.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440b47508190a8a33325b00841dc |
completed | April 20, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07f6d052948190a7361c24a7c3095b |
completed | May 16, 2026, 4:47 a.m. |
Created at: April 10, 2026, 1:46 p.m.