Triple
T28107482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Formula One World Championship |
E710401
|
entity |
| Predicate | recordMostWinsInSeason |
P35351
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [2004 Formula One World Championship, recordMostWinsInSeason, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordMostWinsInSeason Context triple: [2004 Formula One World Championship, recordMostWinsInSeason, 13]
-
A.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
B.
winsInSingleSeason
chosen
Indicates that one entity achieves a specified number of wins within a single competitive season.
-
C.
seasonsWithMostWinsInAL
Indicates the seasons in which a team achieved its highest number of wins specifically in the American League.
-
D.
singleSeasonHitsRecord
Indicates that an entity holds the record for the highest number of hits achieved within a single season.
-
E.
championRegularSeasonRecord
Indicates that an entity is the champion associated with a particular regular season record.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 9:09 p.m.