Triple
T23353879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islands of the Lake District |
E592991
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Ramp Holme |
—
|
NE NERFINISHED |
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: Ramp Holme | Statement: [Islands of the Lake District, hasPart, Ramp Holme]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ramp Holme Context triple: [Islands of the Lake District, hasPart, Ramp Holme]
-
A.
Ramp Holme
chosen
Ramp Holme is one of the small islands located on Windermere, England’s largest natural lake in the Lake District.
-
B.
Rough Holme
Rough Holme is a small, wooded island located on Windermere in England’s Lake District.
-
C.
Long Holme
Long Holme is an alternative name for Belle Isle, a small island in England’s Lake District known for its scenic setting on Windermere.
-
D.
Grass Holme
Grass Holme is one of the small islands located on Windermere, England’s largest natural lake in the Lake District.
-
E.
Arkinholme
Arkinholme is a historic location in Scotland known primarily as the site of the Battle of Arkinholme during the 15th-century conflicts among Scottish noble families.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a15d0a48190862179254c09c6d1 |
completed | April 29, 2026, 5:41 a.m. |
Created at: April 17, 2026, 5:20 p.m.