Triple
T36075359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brawn GP |
E1043481
|
entity |
| Predicate | competedInSeason |
P140691
|
FINISHED |
| Object | 2009 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: 2009 Formula One World Championship | Statement: [Brawn GP, competedInSeason, 2009 Formula One World Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedInSeason Context triple: [Brawn GP, competedInSeason, 2009 Formula One World Championship]
-
A.
isMultiSeasonParticipantOf
Indicates that an entity has participated in the related entity across multiple seasons or iterations.
-
B.
seasonParticipatedIn
chosen
Indicates that an entity took part in or was active during a specific season of a recurring event, series, or competition.
-
C.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
D.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
E.
leagueSeasonParticipatedIn
Indicates that an entity took part in a specific season of a league.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:08 p.m.