Triple
T26389712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Powertrains (Honda-based) |
E663377
|
entity |
| Predicate | predecessorPowerUnitSupplier |
P170626
|
FINISHED |
| Object | Honda Racing F1 |
—
|
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: Honda Racing F1 | Statement: [Red Bull Powertrains (Honda-based), predecessorPowerUnitSupplier, Honda Racing F1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorPowerUnitSupplier Context triple: [Red Bull Powertrains (Honda-based), predecessorPowerUnitSupplier, Honda Racing F1]
-
A.
predecessorChassisCode
Indicates that one chassis code directly precedes another in a chronological or generational sequence.
-
B.
predecessorFranchise
Indicates that one franchise directly precedes and is succeeded by another franchise in a series or lineage.
-
C.
predecessorCompany
Indicates that one company previously existed in a role or form that was succeeded or replaced by another company.
-
D.
successorManufacturer
Indicates that one manufacturer has taken over, replaced, or continued the role or operations of another manufacturer as its successor.
-
E.
predecessorSystem
Indicates that one system existed or was in use before and was replaced or superseded by another system.
- 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_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 26, 2026, 11:24 p.m.