Triple
T17162002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Hamble |
E416503
|
entity |
| Predicate | hasMouthNear |
P350
|
FINISHED |
| Object | Hamble-le-Rice |
E368721
|
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: Hamble-le-Rice | Statement: [River Hamble, hasMouthNear, Hamble-le-Rice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hamble-le-Rice Context triple: [River Hamble, hasMouthNear, Hamble-le-Rice]
-
A.
Hamble-le-Rice
chosen
Hamble-le-Rice is a coastal village in Hampshire, England, known for its yachting, marinas, and location on the River Hamble.
-
B.
Hamble Harbour
Hamble Harbour is a well-known marina and sailing hub on the River Hamble in Hampshire, England, popular with yachtsmen and recreational boaters.
-
C.
Tenterden
Tenterden is a historic market town in Kent, England, known for its traditional high street, heritage railway, and surrounding Wealden countryside.
-
D.
Brightlingsea
Brightlingsea is a coastal town in Essex, England, historically known for its maritime trade, shipbuilding, and association with the medieval Cinque Ports confederation.
-
E.
Henham
Henham is a small rural village located in the English county of Suffolk.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f91258648190a40396067ba5ecd3 |
completed | April 18, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01483969a48190a90268c9560b8cd7 |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:37 a.m.