Triple
T13242816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Women’s Tag Team Championship |
E315321
|
entity |
| Predicate | hasTagTeamFormat |
P63540
|
FINISHED |
| Object | standard tag rules |
—
|
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: standard tag rules | Statement: [WWE Women’s Tag Team Championship, hasTagTeamFormat, standard tag rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTagTeamFormat Context triple: [WWE Women’s Tag Team Championship, hasTagTeamFormat, standard tag rules]
-
A.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
B.
hasRivalryFormat
Indicates that there is a specific structure, set of rules, or format that defines how a rivalry between entities is conducted or organized.
-
C.
hasHomeAndAwayFormat
Indicates that a competition, match, or series is structured with both home and away legs or fixtures between the same opponents.
-
D.
hasTeamStructure
chosen
Indicates that an entity is organized into, or associated with, a specific arrangement of teams or team hierarchy.
-
E.
hasHeroTeam
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
- 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_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.