Triple

T21852745
Position Surface form Disambiguated ID Type / Status
Subject Abernathy E539543 entity
Predicate hasVariantSpelling P457 FINISHED
Object Abernethy 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: Abernethy | Statement: [Abernathy, hasVariantSpelling, Abernethy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abernethy
Context triple: [Abernathy, hasVariantSpelling, Abernethy]
  • A. Abernethy chosen
    Abernethy is a historic Scottish locality known for its early Christian monastic site and ancient Pictish heritage.
  • B. Erskine
    Erskine is a masculine given name of Scottish origin, traditionally used as both a first name and a surname.
  • C. Erskine
    Erskine is a town in Renfrewshire, Scotland, situated on the southern bank of the River Clyde and known for the Erskine Bridge that connects it to West Dunbartonshire.
  • D. Corstorphine
    Corstorphine is a suburban area of Edinburgh, Scotland, known for its residential character, historic village core, and proximity to Edinburgh Zoo.
  • E. Elphinstone
    Elphinstone is a small village in East Lothian, Scotland, known for its rural character and proximity to the town of Tranent.
  • 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_69e0c47829648190bbe2d1d7033768ec completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0bd5a86f48190aa7fb6cd6c3479a2 completed April 28, 2026, 1:59 p.m.
Created at: April 16, 2026, 6:56 p.m.