Triple

T12787230
Position Surface form Disambiguated ID Type / Status
Subject Boomer E305662 entity
Predicate reasonForNotoriety P100753 FINISHED
Object suggestive cannon-inspired appearance LITERAL 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: suggestive cannon-inspired appearance | Statement: [Boomer, reasonForNotoriety, suggestive cannon-inspired appearance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForNotoriety
Context triple: [Boomer, reasonForNotoriety, suggestive cannon-inspired appearance]
  • A. possibleCauseOfNotability chosen
    Indicates that one entity is a potential reason or contributing factor for why another entity is notable or recognized.
  • B. inceptionOfNotoriety
    Indicates the point or event at which an entity first becomes widely known or gains significant public notoriety.
  • C. notableFor
    Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
  • D. sonNotableFor
    Indicates that a son is recognized or distinguished for a particular achievement, role, or characteristic.
  • E. subjectNotableFor
    Indicates that the subject is especially recognized or distinguished for a particular attribute, achievement, role, or characteristic.
  • F. None of above.

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_69d7bdf366888190a8cccb982606889c completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e5dbdb88190a1b06721ada51627 completed April 10, 2026, 9:40 p.m.
PD Predicate disambiguation batch_69d9640ba0688190973e4e7ec8d4a8e0 completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:29 p.m.