Triple
T36119889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda Racing F1 Team |
E1044713
|
entity |
| Predicate | engineCustomerFor |
P17328
|
FINISHED |
| Object | British American 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: British American Racing | Statement: [Honda Racing F1 Team, engineCustomerFor, British American Racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineCustomerFor Context triple: [Honda Racing F1 Team, engineCustomerFor, British American Racing]
-
A.
engineSupplier
chosen
Indicates a relationship where one entity supplies or provides engines to another entity.
-
B.
launchCustomer
Indicates that an entity serves as an initial or flagship customer involved in the launch or early adoption of another entity’s product, service, or initiative.
-
C.
engineName
Indicates the specific name assigned to an engine associated with an entity.
-
D.
exportCustomer
Indicates initiating the transfer or output of customer-related data from one system or context to another, typically for integration, backup, or reporting purposes.
-
E.
launchServiceCustomer
Indicates that a customer is the recipient or user of a launch service provided by another entity.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.