Triple
T26389687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Powertrains (Honda-based) |
E663377
|
entity |
| Predicate | originatesFromManufacturer |
P160003
|
FINISHED |
| Object | Honda |
—
|
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 | Statement: [Red Bull Powertrains (Honda-based), originatesFromManufacturer, Honda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromManufacturer Context triple: [Red Bull Powertrains (Honda-based), originatesFromManufacturer, Honda]
-
A.
usedByManufacturer
Indicates that a manufacturer makes use of a particular resource, component, method, or tool in its production or operational processes.
-
B.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
-
C.
formerManufacturer
Indicates that an entity previously manufactured another entity but no longer does so.
-
D.
machineOrigin
chosen
Indicates that one entity is the source, creator, or place of manufacture for a machine-related entity.
-
E.
ownerOrManufacturer
Indicates that the related entity either owns the item or is the entity that manufactured it.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 26, 2026, 11:24 p.m.