Triple

T21282428
Position Surface form Disambiguated ID Type / Status
Subject Arvid Horn E524558 entity
Predicate familyName P18 FINISHED
Object Horn 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: Horn | Statement: [Arvid Horn, familyName, Horn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horn
Context triple: [Arvid Horn, familyName, Horn]
  • A. Horn chosen
    Horn is a surname most prominently associated with English music producer and musician Trevor Horn, known for his influential work in pop and rock music.
  • B. Horns
    Horns is a dark fantasy-horror novel by Joe Hill that follows a man who mysteriously grows devilish horns and gains disturbing supernatural powers after being accused of his girlfriend’s murder.
  • C. Boss Horn
    "Boss Horn" is a 1966 hard bop jazz album by trumpeter Blue Mitchell, noted for its soulful compositions and strong ensemble arrangements.
  • D. Horn af Rantzien
    Horn af Rantzien is a Swedish noble family name associated with figures such as diplomat Henning Rudolf Horn af Rantzien.
  • E. Kornhorn
    Kornhorn is a small village in the Dutch province of Groningen, known as part of the rural municipality of Grootegast.
  • 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_69e0b5171f6c8190a5d57201ede73811 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e736d249fc8190b0b310467ddeac3c completed April 21, 2026, 8:35 a.m.
Created at: April 16, 2026, 4:02 p.m.