Triple
T36075433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British American Racing |
E1043482
|
entity |
| Predicate | notableSponsorBrand |
P82974
|
FINISHED |
| Object | Lucky Strike |
E58439
|
NE 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: Lucky Strike | Statement: [British American Racing, notableSponsorBrand, Lucky Strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSponsorBrand Context triple: [British American Racing, notableSponsorBrand, Lucky Strike]
-
A.
sponsorshipBrand
chosen
Indicates that one entity serves as a sponsoring brand for another entity, typically providing support, funding, or endorsement.
-
B.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
C.
notablePartner
Indicates that two entities are or have been significant partners, typically in a prominent or noteworthy personal or professional relationship.
-
D.
sponsorBrandType
Indicates the type or category of brand that is acting as a sponsor in the relationship.
-
E.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
- F. None of above.
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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d53c9ab08190bc97d2a4c17336a3 |
completed | June 22, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.