Triple
T26461676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT |
E665654
|
entity |
| Predicate | usedByEngineCustomerTeam |
P30081
|
FINISHED |
| Object | Red Bull power unit customer |
—
|
LITERAL FINISHED |
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 power unit customer | Statement: [AT, usedByEngineCustomerTeam, Red Bull power unit customer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByEngineCustomerTeam Context triple: [AT, usedByEngineCustomerTeam, Red Bull power unit customer]
-
A.
usedForTeam
Indicates that something is utilized or designated for use by a particular team.
-
B.
usedByTeam
chosen
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
C.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
-
D.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
E.
usesSpecEngine
Indicates that one entity employs or relies on a specific engine as its underlying mechanism or processing component.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 12:13 a.m.