Triple
T30699409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMLL World Trios Championship |
E781569
|
entity |
| Predicate | teamCompositionRequirement |
P27972
|
FINISHED |
| Object | fixed trio |
—
|
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: fixed trio | Statement: [CMLL World Trios Championship, teamCompositionRequirement, fixed trio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamCompositionRequirement Context triple: [CMLL World Trios Championship, teamCompositionRequirement, fixed trio]
-
A.
typicalTeamComposition
Indicates the usual or standard combination of roles or members that make up a team.
-
B.
teamConstraint
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
-
C.
rosterRequirement
chosen
Indicates that one entity specifies or imposes a required composition, number, or type of participants that must be included in another entity’s roster.
-
D.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
E.
teamIncludes
Indicates that a particular team has a specified member or entity as part of its composition.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68bdda9dc8190b949ac31d7a79273 |
completed | May 2, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:34 p.m.