Triple

T20319862
Position Surface form Disambiguated ID Type / Status
Subject Castle Tioram E492179 entity
Predicate near P350 FINISHED
Object Acharacle 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: Acharacle | Statement: [Castle Tioram, near, Acharacle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Acharacle
Context triple: [Castle Tioram, near, Acharacle]
  • A. Acharacle chosen
    Acharacle is a small rural village on the west coast of the Scottish Highlands, serving as a local hub for nearby communities on the Ardnamurchan peninsula.
  • B. Chararic
    Chararic was an early medieval king of the Suebi in Galicia, known primarily from sparse historical references to his rule during the post-Roman period in the Iberian Peninsula.
  • C. Chachro
    Chachro is a town in Pakistan’s Sindh province, known for its location in the Thar Desert and its predominantly Hindu Thari community.
  • D. Aptoryama
    Aptoryama is a specific Vedic soma sacrifice ritual recognized as a variant form of the Somayajna.
  • E. Haroeris
    Haroeris is an ancient Egyptian falcon-headed god, a form of Horus associated with kingship, protection, and healing.
  • 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_69e0b4a0134081909113563e1c3ba68a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6778abd14819098a01fd32217fdde completed April 20, 2026, 6:59 p.m.
Created at: April 16, 2026, 11:20 a.m.