Triple

T16585804
Position Surface form Disambiguated ID Type / Status
Subject Elsinore Castle E402953 entity
Predicate alsoKnownAs P39 FINISHED
Object Elsinore E223432 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: Elsinore | Statement: [Elsinore Castle, alsoKnownAs, Elsinore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elsinore
Context triple: [Elsinore Castle, alsoKnownAs, Elsinore]
  • A. Elsinore chosen
    Elsinore is the original name of the Southern California city now known as Lake Elsinore, a community situated by a large natural freshwater lake in Riverside County.
  • B. Elsinore Corona
    Elsinore Corona is a prominent circular tectonic feature on Uranus’s moon Miranda, characterized by its complex ridges, troughs, and dramatic geological deformation.
  • C. Barden
    Barden is a small village in North Yorkshire, England, known for its scenic location in Wharfedale within the Yorkshire Dales.
  • D. Vinge
    Vinge is a surname most notably associated with Vernor Vinge, the American science fiction author and mathematician known for popularizing the concept of the technological singularity.
  • E. Hampoort
    Hampoort is a historic city gate, likely part of the old fortifications of a European town or 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3599cbc448190bc80eef4ad58eb41 completed April 18, 2026, 10:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006ef4f17c819095b3c6f8644b687b completed May 10, 2026, 11:41 a.m.
Created at: April 10, 2026, 5:16 a.m.