Triple

T18187196
Position Surface form Disambiguated ID Type / Status
Subject I’ll Overcome Someday E435444 entity
Predicate hasNotableMotive P642 FINISHED
Object “I’ll overcome” phrase 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: “I’ll overcome” phrase | Statement: [I’ll Overcome Someday, hasNotableMotive, “I’ll overcome” phrase]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableMotive
Context triple: [I’ll Overcome Someday, hasNotableMotive, “I’ll overcome” phrase]
  • A. hasMotiveOfCriminals
    Indicates that the specified motive is attributed to or associated with the criminals in question.
  • B. hasNotableSubject
    Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
  • C. hasMotiveContext
    Indicates that there is contextual information explaining the reasons or motivations behind an action, event, or relationship.
  • D. hasMotiveElement
    Indicates that one entity includes, specifies, or is characterized by a particular motive-related component or factor in a broader relationship or action.
  • E. hasNotableFeature chosen
    Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
  • 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_69d8b90c7ec081909b4694ccecb449c6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dfff86b8819080324aafba77acf3 completed April 19, 2026, 2 p.m.
PD Predicate disambiguation batch_69e4331e92408190ad607ba4956a3897 completed April 19, 2026, 1:42 a.m.
Created at: April 10, 2026, 10:31 a.m.