Triple

T22609232
Position Surface form Disambiguated ID Type / Status
Subject Belle Isle E566647 entity
Predicate hasAlternativeName P39 FINISHED
Object Long 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: Long Holme | Statement: [Belle Isle, hasAlternativeName, Long Holme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Long Holme
Context triple: [Belle Isle, hasAlternativeName, Long Holme]
  • A. Long Holme chosen
    Long Holme is an alternative name for Belle Isle, a small island in England’s Lake District known for its scenic setting on Windermere.
  • B. Holme Valley
    Holme Valley is a rural valley in West Yorkshire, England, known for its picturesque landscapes, traditional stone-built villages, and location within the South Pennines.
  • C. Holme
    Holme is a surname and place name of English origin that appears as a variant of the more common name "Holmes."
  • D. Holme
    Holme is a residential neighborhood located in the southern part of Aarhus, Denmark.
  • E. Holme Low
    Holme Low is a civil parish and rural area in Cumbria, England, known for its agricultural landscape and small settlements near the Solway Firth.
  • 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_69e245884860819081046ce07d5872c4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f167e9245c81908e36ffcd16737a9d completed April 29, 2026, 2:07 a.m.
Created at: April 17, 2026, 2:56 p.m.