Triple
T11919797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exmoor |
E283623
|
entity |
| Predicate | hasHighestPoint |
P210
|
FINISHED |
| Object | Dunkery Beacon |
E772544
|
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: Dunkery Beacon | Statement: [Exmoor, hasHighestPoint, Dunkery Beacon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dunkery Beacon Context triple: [Exmoor, hasHighestPoint, Dunkery Beacon]
-
A.
Dunkery Beacon
chosen
Dunkery Beacon is the highest summit on Exmoor and in Somerset, England, known for its sweeping moorland views and prominent cairn.
-
B.
Penrith Beacon
Penrith Beacon is a historic hilltop monument and viewpoint overlooking the town of Penrith in Cumbria, England.
-
C.
Bodmin Beacon
Bodmin Beacon is a prominent hilltop monument and local nature reserve overlooking the town of Bodmin in Cornwall, England.
-
D.
Firle Beacon
Firle Beacon is a prominent chalk hill and viewpoint on the South Downs in East Sussex, England, known for its sweeping countryside and coastal vistas.
-
E.
Bredon Hill
Bredon Hill is a prominent hill in Worcestershire, England, known for its Iron Age hill fort, scenic walking routes, and rich wildlife.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f440247cf4819084567f6e1005ef04 |
completed | May 1, 2026, 5:54 a.m. |
Created at: April 8, 2026, 9:44 p.m.