Triple

T5962813
Position Surface form Disambiguated ID Type / Status
Subject Bruce Cockburn E132679 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: [Bruce Cockburn, familyName, Cockburn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cockburn
Context triple: [Bruce 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. Heathcote
    Heathcote is a residential area or property in Ilkley, West Yorkshire, England, notable enough to have given its name to the surrounding locality.
  • D. Fairburn
    Fairburn is a small suburban city in Fulton County, Georgia, that forms part of the greater Atlanta metropolitan area.
  • E. Cleland
    Cleland is a village in North Lanarkshire, Scotland, known historically for its coal mining heritage and proximity to Motherwell and Wishaw.
  • 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_69c0086c2364819091e9fe2f58fa2517 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c03a00e444819087f9df62263e83dc completed March 22, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11ccdec948190a0792c351a6867b7 completed March 23, 2026, 10:58 a.m.
Created at: March 22, 2026, 4:03 p.m.