Triple

T35249860
Position Surface form Disambiguated ID Type / Status
Subject Shibboleth incident E1018066 entity
Predicate involvesPronunciationOf P196017 FINISHED
Object shibboleth 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: shibboleth | Statement: [Shibboleth incident, involvesPronunciationOf, shibboleth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: involvesPronunciationOf
Context triple: [Shibboleth incident, involvesPronunciationOf, shibboleth]
  • A. involves
    Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
  • B. avoidsPronunciationOf
    Indicates that one entity deliberately refrains from saying or articulating the name, word, or expression associated with another entity.
  • C. isMorePronouncedIn
    Indicates that a particular feature, quality, or effect appears with greater intensity or prominence in one context, entity, or condition than in another.
  • D. correctPronunciation
    Indicates that one entity provides the accurate or standard way to pronounce another entity (such as a word or name).
  • E. typeOfPronunciationDescribed
    Indicates that one entity specifies or characterizes the kind or style of pronunciation associated with another entity.
  • F. None of above. chosen

Provenance (4 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_69f76de407d081909dfc3c419817ae93 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fe00dad1708190b6522476bebb43af completed May 8, 2026, 3:27 p.m.
PD Predicate disambiguation batch_69fdfc3717f48190bb50ac2919c8ef95 completed May 8, 2026, 3:07 p.m.
PDg Predicate description generation batch_69fe00d8d8248190a63c12aa2c2f7c0c completed May 8, 2026, 3:27 p.m.
Created at: May 3, 2026, 4:02 p.m.