Triple
T22706809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria national football team |
E561477
|
entity |
| Predicate | largestWin |
P149395
|
FINISHED |
| Object | Austria 9–0 Malta |
—
|
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: Austria 9–0 Malta | Statement: [Austria national football team, largestWin, Austria 9–0 Malta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestWin Context triple: [Austria national football team, largestWin, Austria 9–0 Malta]
-
A.
mostOverallWinsRecord
Indicates that the subject holds the record for having the greatest total number of wins compared to all others in the relevant context.
-
B.
mostConsecutiveWinsCount
Indicates the highest number of wins achieved in a row within a given sequence or context.
-
C.
mostGamesWonBy
Indicates that one entity holds the record for having won the greatest number of games compared to others in a given context.
-
D.
mostConsecutiveWinsPlayer
Indicates the player who holds the record for the highest number of consecutive wins within a given context or competition.
-
E.
winsLeader
Indicates that one entity achieves victory or leadership over another in a competitive or comparative context.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178ceba6c8190a538366a8e4648de |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:17 p.m.