Triple
T13246849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SmackDown Tag Team Championship |
E315426
|
entity |
| Predicate | competedForBy |
P32080
|
FINISHED |
| Object | male tag teams |
—
|
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: male tag teams | Statement: [SmackDown Tag Team Championship, competedForBy, male tag teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedForBy Context triple: [SmackDown Tag Team Championship, competedForBy, male tag teams]
-
A.
competedFor
chosen
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
-
B.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
C.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
D.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
E.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5c09f88190bb1566a6d8c073a6 |
completed | April 10, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69d98bcca7d88190a3e68e99ed3a29e6 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.