Triple
T37817820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big East Men's Soccer Tournament |
E942823
|
entity |
| Predicate | usesPenaltyKicksToDecideTies |
P12108
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Big East Men's Soccer Tournament, usesPenaltyKicksToDecideTies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPenaltyKicksToDecideTies Context triple: [Big East Men's Soccer Tournament, usesPenaltyKicksToDecideTies, true]
-
A.
usesPenaltyShootouts
chosen
Indicates that the outcome of a match or competition is decided by conducting penalty shootouts.
-
B.
penaltyGoalPoints
Indicates that points are awarded for a goal scored from a penalty situation.
-
C.
penaltyShootoutOccurred
Indicates that a penalty shootout took place to decide the outcome of a match or contest.
-
D.
goldenGoalRuleUsed
Indicates that the outcome of a match or competition was determined using the golden goal rule, where the first score in extra time immediately ends the game.
-
E.
penaltyScoredBy
Indicates that a penalty (typically in a game or sport) was successfully converted or scored by a particular participant.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:19 p.m.