Triple

T16473447
Position Surface form Disambiguated ID Type / Status
Subject Invermark E400125 entity
Predicate locatedNear P294 FINISHED
Object Invermark Castle 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: Invermark Castle | Statement: [Invermark, locatedNear, Invermark Castle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Invermark Castle
Context triple: [Invermark, locatedNear, Invermark Castle]
  • A. Invermark Castle chosen
    Invermark Castle is a ruined 16th-century tower house in Angus, Scotland, historically built to guard the route through Glen Esk.
  • B. Inverugie Castle
    Inverugie Castle is a ruined medieval stronghold in Aberdeenshire, Scotland, historically associated with the powerful Keith family.
  • C. Inveruglas Castle
    Inveruglas Castle is a ruined medieval stronghold on Loch Lomond in Scotland, historically associated with the Clan MacFarlane.
  • D. Ardvreck Castle
    Ardvreck Castle is a ruined 16th-century fortress dramatically situated on the shores of Loch Assynt in the Scottish Highlands.
  • E. Moura Castle
    Moura Castle is a historic medieval fortress located in the town of Moura in Portugal, known for its defensive walls and strategic role in the region’s history.
  • 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32dd266c48190991a1484eb2f7bcc completed April 18, 2026, 7:08 a.m.
Created at: April 10, 2026, 5:11 a.m.