Triple
T22730409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highdown Hill |
E562117
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Worthing |
—
|
NE NERFINISHED |
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: Worthing | Statement: [Highdown Hill, hasViewOf, Worthing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Worthing Context triple: [Highdown Hill, hasViewOf, Worthing]
-
A.
Worthing
Worthing is a small city in Lincoln County, South Dakota, known as a residential community within the Sioux Falls metropolitan area.
-
B.
Worthing
chosen
Worthing is a large seaside town and resort on the south coast of England in West Sussex.
-
C.
Hove
Hove is a small, affluent municipality in the Belgian province of Antwerp, known for its residential character and green surroundings.
-
D.
Hove
Hove is a coastal village on the island of Tromøya in Arendal Municipality, Agder county, Norway, known for its scenic beaches and outdoor recreation areas.
-
E.
Hove
Hove is a coastal town in East Sussex, England, forming part of the city of Brighton and Hove on the south coast.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792cb9cc8190a7c45032427bca1a |
completed | April 29, 2026, 3:21 a.m. |
Created at: April 17, 2026, 3:21 p.m.