Triple
T35807314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Joseph Copeland |
E1035133
|
entity |
| Predicate | wrestlingTagTeam |
P167341
|
FINISHED |
| Object | Edge and Christian |
—
|
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: Edge and Christian | Statement: [Adam Joseph Copeland, wrestlingTagTeam, Edge and Christian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrestlingTagTeam Context triple: [Adam Joseph Copeland, wrestlingTagTeam, Edge and Christian]
-
A.
twinTagTeam
Indicates a cooperative relationship where two twin entities act together as a coordinated team in performing an action or achieving a goal.
-
B.
hasTagTeamExperienceWith
chosen
Indicates that two entities have previously participated together as partners in a tag team context.
-
C.
hasTagTeamDivision
Indicates that an entity participates in or is associated with a tag team division, typically involving teams of multiple members competing together.
-
D.
hasTagTeamType
Indicates that an entity participates in or is associated with a specific type or category of tag team.
-
E.
wrestlingStable
Indicates that multiple wrestlers are part of the same organized wrestling group or faction.
- 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_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:06 p.m.