Triple
T26389690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Powertrains (Honda-based) |
E663377
|
entity |
| Predicate | suppliesTeam |
P160586
|
FINISHED |
| Object | Oracle Red Bull Racing |
—
|
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: Oracle Red Bull Racing | Statement: [Red Bull Powertrains (Honda-based), suppliesTeam, Oracle Red Bull Racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliesTeam Context triple: [Red Bull Powertrains (Honda-based), suppliesTeam, Oracle Red Bull Racing]
-
A.
supportsTeam
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
-
B.
supportsTeamFrom
Indicates that one entity actively backs, favors, or roots for a particular team.
-
C.
performsForTeam
Indicates that an individual carries out actions or duties on behalf of, or in representation of, a specific team.
-
D.
coversTeam
Indicates that one entity provides reporting, media coverage, or journalistic attention to a specific team.
-
E.
teamworkOption
Indicates that multiple entities collaborate or work together as a coordinated team to achieve a shared goal or perform a joint action.
- F. None of above. chosen
Provenance (4 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610be3e848190b7acb7675e37e1f5 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 11:24 p.m.