Triple
T13252115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allsvenskan |
E315557
|
entity |
| Predicate | hasOutcomeForWinner |
P14027
|
FINISHED |
| Object | national champion of Sweden |
—
|
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: national champion of Sweden | Statement: [Allsvenskan, hasOutcomeForWinner, national champion of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeForWinner Context triple: [Allsvenskan, hasOutcomeForWinner, national champion of Sweden]
-
A.
subsequentOutcomeForWinner
chosen
Indicates that the predicate links a winner to an outcome or event that occurs to or for them after their initial victory.
-
B.
playerOutcome
Indicates the result or consequence experienced by a player in a game, match, or scenario (such as winning, losing, or drawing).
-
C.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
D.
hasWinnerType
Indicates that an entity has a specific type or category of winner associated with it.
-
E.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:24 p.m.