Triple
T35807190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Phenom |
E1035130
|
entity |
| Predicate | hasTagTeamName |
P116479
|
FINISHED |
| Object | The Brothers of Destruction |
—
|
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: The Brothers of Destruction | Statement: [The Phenom, hasTagTeamName, The Brothers of Destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTagTeamName Context triple: [The Phenom, hasTagTeamName, The Brothers of Destruction]
-
A.
hasTagTeamDivision
Indicates that an entity participates in or is associated with a tag team division, typically involving teams of multiple members competing together.
-
B.
hasTagTeamExperienceWith
Indicates that two entities have previously participated together as partners in a tag team context.
-
C.
twinTagTeam
Indicates a cooperative relationship where two twin entities act together as a coordinated team in performing an action or achieving a goal.
-
D.
hasSiblingTagTeam
Indicates that two entities are siblings who participate together as a tag team in a shared activity or context.
-
E.
hasCompanionTeamName
chosen
Indicates that an entity is associated with a companion team identified by the given team name.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:06 p.m.