Triple
T10347524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 Major League Soccer season |
E243788
|
entity |
| Predicate | usesShootoutToDecideDraws |
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: [1997 Major League Soccer season, usesShootoutToDecideDraws, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesShootoutToDecideDraws Context triple: [1997 Major League Soccer season, usesShootoutToDecideDraws, true]
-
A.
hasShootoutInLeague
Indicates that a league match involved a shootout (e.g., penalty or tiebreak shootout) as part of its outcome or progression.
-
B.
pointsForShootoutWin
Indicates the number of points awarded to a team for winning a game via a shootout.
-
C.
decidingMethodForDrawnFinals
Indicates the method or procedure used to determine the outcome or winner when a final match or contest ends in a draw.
-
D.
usesPenaltyShootouts
chosen
Indicates that the outcome of a match or competition is decided by conducting penalty shootouts.
-
E.
hasKnockoutStageDraw
Indicates that an event or competition includes a defined draw or bracket structure for its knockout stage matches.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9251654819080d1e3f0ed4ee9d3 |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:56 a.m.