Triple

T35807674
Position Surface form Disambiguated ID Type / Status
Subject E&C’s Pod of Awesomeness E1035142 entity
Predicate hostRealNameOf P9233 FINISHED
Object Adam Copeland 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: Adam Copeland | Statement: [E&C’s Pod of Awesomeness, hostRealNameOf, Adam Copeland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hostRealNameOf
Context triple: [E&C’s Pod of Awesomeness, hostRealNameOf, Adam Copeland]
  • A. hostFullName
    Indicates that one entity is the complete personal name (including given and family names, and possibly middle names or titles) of the host associated with another entity.
  • B. realName chosen
    Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
  • C. notRealNameOf
    Indicates that the referenced name is not the entity’s actual or official name (e.g., it is false, fabricated, or otherwise not the real name of that entity).
  • D. realWorldName
    Indicates that an entity’s name in a real-world context is given or associated with another value.
  • E. nameRepresents
    Indicates that a given name stands for, denotes, or is used to identify a particular entity.
  • 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_69f76e1762408190b885a8456862e372 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7aa699d68819081ed363931894ab3 completed May 3, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69f7a8d219f8819081dc4ce3c83ca0cb completed May 3, 2026, 7:58 p.m.
Created at: May 3, 2026, 4:06 p.m.