Triple
T24405673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Raw Tag Team Championship |
E615302
|
entity |
| Predicate | submissionDecidesWinner |
P156080
|
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 Raw Tag Team Championship, submissionDecidesWinner, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submissionDecidesWinner Context triple: [WWE Raw Tag Team Championship, submissionDecidesWinner, yes]
-
A.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
B.
submissionBasis
Indicates the basis, criteria, or grounds on which something is submitted or filed (e.g., a document, application, or claim).
-
C.
submissionSystem
Indicates a relationship where something is provided or turned in through a designated system or platform for receiving submissions.
-
D.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
E.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294de76848190bd2cf3c7add2dcf1 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:05 a.m.