Triple
T3145202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIS Ski Jumping World Cup events |
E65745
|
entity |
| Predicate | seasonOutcome |
P8651
|
FINISHED |
| Object | overall World Cup champion |
—
|
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: overall World Cup champion | Statement: [FIS Ski Jumping World Cup events, seasonOutcome, overall World Cup champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonOutcome Context triple: [FIS Ski Jumping World Cup events, seasonOutcome, overall World Cup champion]
-
A.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
B.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
C.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
-
D.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
E.
competitionResult
chosen
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59797788190a8d71262888c5df0 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.