Triple
T26461666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT |
E665654
|
entity |
| Predicate | usedFromSeason |
P73853
|
FINISHED |
| Object | 2020 Formula One World Championship |
—
|
NE NERFINISHED |
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: 2020 Formula One World Championship | Statement: [AT, usedFromSeason, 2020 Formula One World Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFromSeason Context triple: [AT, usedFromSeason, 2020 Formula One World Championship]
-
A.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
B.
hasUseSeason
Indicates the season or time of year during which something is intended or suitable to be used.
-
C.
usedForSeasonRange
Indicates the span of seasons or time period during which something is intended or suitable to be used.
-
D.
playedFromSeason
chosen
Indicates the starting season from which an entity (such as a player or participant) began playing for or being active with another entity (such as a team or organization).
-
E.
firstUsedInSeason
Indicates the season in which something (such as a character, item, or concept) was first introduced or used.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 12:13 a.m.