Triple
T9586858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avon Gorge |
E231311
|
entity |
| Predicate | mouthNear |
P18935
|
FINISHED |
| Object | Avonmouth |
E231309
|
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: Avonmouth | Statement: [Avon Gorge, mouthNear, Avonmouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Avonmouth Context triple: [Avon Gorge, mouthNear, Avonmouth]
-
A.
Avonmouth
chosen
Avonmouth is a port and industrial district on the Severn Estuary near Bristol in southwest England.
-
B.
Avonmouth Docks
Avonmouth Docks is a major commercial port complex near Bristol, England, handling a wide range of cargo and serving as an important hub for regional and international trade.
-
C.
Nailsea
Nailsea is a small town in North Somerset, England, historically known for its glassmaking and coal mining industries.
-
D.
Clevedon
Clevedon is a coastal town in southwest England known for its Victorian pier and views across the Severn Estuary.
-
E.
Shirehampton
Shirehampton is a suburban district of Bristol, England, situated near the River Avon and known for its residential character and transport links into the city.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99eed8288190b74de991bb55b15b |
completed | April 1, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d17917063c819084521bf2e61aee6b |
completed | April 4, 2026, 8:48 p.m. |
Created at: March 30, 2026, 8:06 p.m.