Triple

T16027200
Position Surface form Disambiguated ID Type / Status
Subject Bremanger E388745 entity
Predicate hasMountain P10602 FINISHED
Object Hornelen E366565 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: Hornelen | Statement: [Bremanger, hasMountain, Hornelen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hornelen
Context triple: [Bremanger, hasMountain, Hornelen]
  • A. Hornelen chosen
    Hornelen is a prominent mountain in western Norway, famed for being one of the highest sea cliffs in Europe and a notable landmark for hikers and climbers.
  • B. Hauran
    Hauran is a historical region in southwestern Syria and northwestern Jordan, known for its fertile volcanic plains and ancient settlements.
  • C. Hornschuch
    Hornschuch is a German surname most notably associated with Karl Georg Hornschuch, a 19th-century botanist and bryologist.
  • D. Himring
    Himring is a prominent hill and fortress in J.R.R. Tolkien’s legendarium, serving as Maedhros’s stronghold and a key defensive position in northeastern Beleriand during the First Age.
  • E. Hollein
    Hollein is a German-language surname most prominently associated with Austrian architects Hans Hollein and his son Max Hollein, a leading museum director.
  • 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_69d86dada3808190825d5f80d72fbe88 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e18328707c8190b9a444c78faaaa04 completed April 17, 2026, 12:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffcf33c6a881909284933ea3b7dd6e completed May 10, 2026, 12:20 a.m.
Created at: April 10, 2026, 4:56 a.m.