Triple
T16973498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Lee |
E411747
|
entity |
| Predicate | hasNearbyFeature |
P350
|
FINISHED |
| Object | Queen’s Well |
E1214625
|
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: Queen’s Well | Statement: [Loch Lee, hasNearbyFeature, Queen’s Well]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Queen’s Well Context triple: [Loch Lee, hasNearbyFeature, Queen’s Well]
-
A.
Queen’s Well
chosen
Queen’s Well is a historic stone well in Glen Esk, Angus, Scotland, traditionally associated with a visit by Queen Victoria.
-
B.
Nun’s Well
Nun’s Well is a historic underground water cistern at Gibraltar’s Europa Point, traditionally used as a key freshwater source for the area.
-
C.
Mary’s Well
Mary’s Well is a historic spring and pilgrimage site in Nazareth traditionally associated with the Virgin Mary and the Annunciation.
-
D.
St Ann’s Well
St Ann’s Well is a historic thermal spring in Buxton, England, long associated with spa culture and reputed healing waters.
-
E.
St Ann’s Well
St Ann’s Well is a historic spring and popular visitor spot on the slopes of the Malvern Hills, long associated with the area’s famed mineral waters and spa heritage.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0af06688190a77682aa297cd27e |
completed | April 18, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d4738fbc819099e8281ebc777091 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:31 a.m.