Triple
T13242817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Women’s Tag Team Championship |
E315321
|
entity |
| Predicate | pinfallOrSubmissionRequired |
P108705
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WWE Women’s Tag Team Championship, pinfallOrSubmissionRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pinfallOrSubmissionRequired Context triple: [WWE Women’s Tag Team Championship, pinfallOrSubmissionRequired, yes]
-
A.
requiredSurrenderOf
Indicates that one party is obligated to give up or relinquish something to another party.
-
B.
requiresRefereeSignal
Indicates that the action or event can only proceed or be validated when a referee explicitly signals or authorizes it.
-
C.
requiresJudgeToBe
Indicates that a situation, action, or process necessitates the judge to possess or be in a specific state, role, or condition.
-
D.
hasSubmissionPolicy
Indicates that an entity is associated with a specific set of rules or conditions governing how submissions to it must be made.
-
E.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:23 p.m.