Triple

T1139348
Position Surface form Disambiguated ID Type / Status
Subject Alexander James Edmund Cockburn E23413 entity
Predicate familyName P18 FINISHED
Object Cockburn E23413 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: Cockburn | Statement: [Alexander James Edmund Cockburn, familyName, Cockburn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cockburn
Context triple: [Alexander James Edmund Cockburn, familyName, Cockburn]
  • A. Cockburn chosen
    Cockburn is a Scottish surname historically associated with various notable figures in British military, political, and cultural life.
  • B. Heathcote
    Heathcote is an unincorporated community located within South Brunswick Township in Middlesex County, New Jersey.
  • C. Sholto
    Sholto is a masculine given name of Scottish origin, historically associated with figures such as military leaders and nobles.
  • D. Sculthorpe
    Sculthorpe is a small village in Norfolk, England, known for its rural character and proximity to the market town of Fakenham.
  • E. Kirkwode
    Kirkwode is an alternative spelling of the name Kirkwood, which is used for various places and surnames of primarily Scottish and English origin.
  • 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_69a493ef399c8190b04b9146d2314f59 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc27c88881909c64ec30b7f66575 completed March 1, 2026, 10:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac7f30222081909679902c6e0d4790 completed March 7, 2026, 7:40 p.m.
Created at: March 1, 2026, 7:44 p.m.