Triple
T35809761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-Generation X |
E1035196
|
entity |
| Predicate | signatureTaunt |
P109913
|
FINISHED |
| Object | "Are you ready?" |
—
|
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: "Are you ready?" | Statement: [D-Generation X, signatureTaunt, "Are you ready?"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureTaunt Context triple: [D-Generation X, signatureTaunt, "Are you ready?"]
-
A.
hasSignatureTaunt
chosen
Indicates that an entity possesses a distinctive, characteristic taunting action or gesture uniquely associated with it.
-
B.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
C.
signatureTuneOf
Indicates that one entity is the characteristic or officially recognized musical theme associated with another entity.
-
D.
associatedWithTaunt
Indicates that one entity is linked to, involved in, or characterized by a taunt directed at another entity.
-
E.
signatureTournament
Indicates that an entity is the primary or flagship tournament most closely associated with another entity (such as an organization, player, or series).
- 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_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:06 p.m.