Triple

T37051164
Position Surface form Disambiguated ID Type / Status
Subject Agent Double-O-Soul E917051 entity
Predicate earlySignatureHitOf P55031 FINISHED
Object Edwin Starr 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: Edwin Starr | Statement: [Agent Double-O-Soul, earlySignatureHitOf, Edwin Starr]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: earlySignatureHitOf
Context triple: [Agent Double-O-Soul, earlySignatureHitOf, Edwin Starr]
  • A. isSignatureHitOf
    Indicates that one hit or impact is the characteristic or defining strike associated with a particular entity, event, or performance.
  • B. isSignatureHitFor
    Indicates that one event, action, or data pattern matches and triggers a specific predefined signature (such as a rule, template, or detection pattern).
  • C. isEarlyHitFor chosen
    Indicates that one entity is an initial or precursor success, discovery, or recognition that occurs early in relation to another entity.
  • D. hasSignatureEvent
    Indicates that an entity is associated with a distinctive or defining event that characterizes or highlights it.
  • E. signatureEventOf
    Indicates that a given event represents or records the signing (or creation) of the associated entity, such as a document, agreement, or artifact.
  • 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_69f76e94d0308190a3f06890e133c88e completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb34e5576881909394355c8ec6ddd2 completed May 6, 2026, 12:32 p.m.
PD Predicate disambiguation batch_69fb2f6171e88190bf1e0ee6a644b6a9 completed May 6, 2026, 12:09 p.m.
Created at: May 3, 2026, 4:14 p.m.