Triple
T6024876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Open Cup 2012 |
E134150
|
entity |
| Predicate | finalMatchDecidedBy |
P68822
|
FINISHED |
| Object | penalty shootout |
—
|
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: penalty shootout | Statement: [U.S. Open Cup 2012, finalMatchDecidedBy, penalty shootout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMatchDecidedBy Context triple: [U.S. Open Cup 2012, finalMatchDecidedBy, penalty shootout]
-
A.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
B.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
C.
featuredMatchWinner
Indicates that an entity is the winner of a highlighted or prominently featured match.
-
D.
decisiveMatchAttendance
Indicates that an entity attends a match whose outcome is crucial or decisive, such as determining a championship, qualification, or elimination.
-
E.
finalFirstMatchResult
Indicates that the referenced result is the first outcome in a sequence that is considered final or decisive for a given matching process.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04fbf048081908b0da0cf838730a5 |
completed | March 22, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:07 p.m.