Triple
T26462227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT02 |
E665666
|
entity |
| Predicate | sharesPowerUnitWith |
P177085
|
FINISHED |
| Object | Red Bull Racing RB16B |
—
|
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 RB16B | Statement: [AT02, sharesPowerUnitWith, Red Bull Racing RB16B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPowerUnitWith Context triple: [AT02, sharesPowerUnitWith, Red Bull Racing RB16B]
-
A.
sharesPowerWith
Indicates that two or more entities jointly hold, exercise, or distribute authority or control in a shared manner.
-
B.
sharesPowertrainWith
chosen
Indicates that two entities use the same or a fundamentally identical powertrain system.
-
C.
sharesChassisWith
Indicates that two entities are built on the same underlying structural platform or frame.
-
D.
sharesSpecialistUnitsWith
Indicates that two entities utilize or have access to the same specialized units, teams, or expert resources.
-
E.
sharesOwnershipWith
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
- 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_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 12:13 a.m.