Triple
T24204222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attitude Adjustment |
E600058
|
entity |
| Predicate | hasMatchOutcomeRole |
P23442
|
FINISHED |
| Object | pinfall setup |
—
|
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: pinfall setup | Statement: [Attitude Adjustment, hasMatchOutcomeRole, pinfall setup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchOutcomeRole Context triple: [Attitude Adjustment, hasMatchOutcomeRole, pinfall setup]
-
A.
roleAtMatches
Indicates that an entity’s role or position at a given time or context matches a specified role criterion.
-
B.
battleOutcomeRole
chosen
Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
-
C.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
D.
hasMatch
Indicates that one entity corresponds to, aligns with, or is considered an equivalent or suitable counterpart to another entity.
-
E.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca38c148190ae65cd692567d43d |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.