Triple
T22706812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria national football team |
E561477
|
entity |
| Predicate | largestDefeat |
P51330
|
FINISHED |
| Object | England 11–1 Austria |
—
|
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: England 11–1 Austria | Statement: [Austria national football team, largestDefeat, England 11–1 Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestDefeat Context triple: [Austria national football team, largestDefeat, England 11–1 Austria]
-
A.
dateOfMajorDefeat
Indicates the specific date on which an entity experienced a significant or decisive defeat.
-
B.
significantDefeat
chosen
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
-
C.
largestWorldCupDefeatYear
Indicates the year in which an entity experienced its largest defeat in a World Cup match.
-
D.
largestWorldCupDefeatOpponent
Indicates the opposing team against which an entity suffered its largest margin of defeat in a FIFA World Cup match.
-
E.
locationOfMajorDefeat
Indicates the place where a significant or decisive defeat of a party occurred.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cff7588190a40c8cef0f3cd44a |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:17 p.m.