Triple
T30653583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMLL World Tag Team Championship |
E780325
|
entity |
| Predicate | titleHoldersType |
P22451
|
FINISHED |
| Object | tag team wrestlers |
—
|
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: tag team wrestlers | Statement: [CMLL World Tag Team Championship, titleHoldersType, tag team wrestlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHoldersType Context triple: [CMLL World Tag Team Championship, titleHoldersType, tag team wrestlers]
-
A.
titleHolders
Indicates that one or more entities currently or formerly hold a specified title, position, or honor.
-
B.
titleHolderType
chosen
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
-
C.
titleHoldersWere
Indicates that certain entities previously held a specified title or position during a past period.
-
D.
titleHoldersLinkedTo
Indicates that two or more entities are connected through holding, sharing, or transferring the same title or position.
-
E.
titleHoldersCollectively
Indicates that a group of entities jointly hold, share, or possess a particular title or set of titles as a collective.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 29, 2026, 8:30 p.m.