Triple

T14846767
Position Surface form Disambiguated ID Type / Status
Subject Edzell Woods E349115 entity
Predicate nearbySettlement P350 FINISHED
Object Edzell E101550 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: Edzell | Statement: [Edzell Woods, nearbySettlement, Edzell]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edzell
Context triple: [Edzell Woods, nearbySettlement, Edzell]
  • A. Edzell chosen
    Edzell is a small historic village in Angus, Scotland, known for its picturesque setting, nearby glens, and the ruins of Edzell Castle.
  • B. Gavinton
    Gavinton is a small village in the Scottish Borders region of Scotland, situated near the town of Duns.
  • C. Fairburn
    Fairburn is a small suburban city in Fulton County, Georgia, that forms part of the greater Atlanta metropolitan area.
  • D. Kincorth
    Kincorth is a residential area in the south of Aberdeen, Scotland, known for its post-war housing and proximity to the River Dee.
  • E. Harput
    Harput is an ancient settlement and archaeological site in eastern Turkey known for its historic fortress, churches, and layered cultural heritage spanning multiple civilizations.
  • 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_69d822ec69008190a9232caa68836872 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded29236dc8190b7d3a37d09f9fb21 completed April 14, 2026, 11:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe65010190819083ec051eb5d82839 completed May 8, 2026, 10:34 p.m.
Created at: April 10, 2026, 1:53 a.m.