Triple
T9940141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Arun |
E194056
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Amberley |
E584666
|
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: Amberley | Statement: [River Arun, nearbySettlement, Amberley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amberley Context triple: [River Arun, nearbySettlement, Amberley]
-
A.
Amberley
chosen
Amberley is a picturesque village in West Sussex, England, known for its historic cottages, castle, and scenic setting in the South Downs near the River Arun.
-
B.
Bramber
Bramber is a historic village in West Sussex, England, known for the ruins of Bramber Castle and its picturesque rural setting.
-
C.
Amberlea
Amberlea is a residential neighbourhood located in the city of Pickering in the Greater Toronto Area of Ontario, Canada.
-
D.
Warminster
Warminster is a market town in Wiltshire, England, known for its historic architecture, surrounding countryside, and role as a local transport and service hub.
-
E.
Carlysle
Carlysle is an alternative spelling of the surname and given name "Carlyle," which is of English and Scottish origin.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb60f4ffc8190bfe916bb4a7bf5c5 |
completed | April 2, 2026, 12:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d229080d0081908b66b9c4166db252 |
completed | April 5, 2026, 9:19 a.m. |
Created at: March 30, 2026, 8:44 p.m.