Triple
T26563522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sébastien Buemi |
E666313
|
entity |
| Predicate | testAndReserveDriverFor |
P82785
|
FINISHED |
| Object | 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: Red Bull Racing | Statement: [Sébastien Buemi, testAndReserveDriverFor, Red Bull Racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testAndReserveDriverFor Context triple: [Sébastien Buemi, testAndReserveDriverFor, Red Bull Racing]
-
A.
testAndReserveDriver
chosen
Indicates attempting to verify a driver’s availability and, if available, reserving that driver for a specific task or time slot.
-
B.
hasDriver
Indicates that an entity is operated, controlled, or driven by a specific person or agent.
-
C.
formerDriverOwner
Indicates that an entity once owned a driver (e.g., a vehicle driver or software driver) but no longer does so.
-
D.
associatedWithDriver
Indicates that one entity has a connection or relationship with a specific driver, such as being linked, assigned, or otherwise related to that driver.
-
E.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6149cc0c88190aadaacfa45a2382e |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:54 a.m.