Triple
T32069291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust-eze Racing |
E818966
|
entity |
| Predicate | sponsorTagline |
P53311
|
FINISHED |
| Object | Medicated Bumper Ointment |
—
|
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: Medicated Bumper Ointment | Statement: [Rust-eze Racing, sponsorTagline, Medicated Bumper Ointment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorTagline Context triple: [Rust-eze Racing, sponsorTagline, Medicated Bumper Ointment]
-
A.
taglineMatch
Indicates that two entities share the same tagline or that a tagline corresponds to a given entity.
-
B.
taglineForm
chosen
Indicates that one entity serves as the tagline or slogan associated with another entity.
-
C.
sponsorFrom
Indicates that one entity provides sponsorship or financial backing originating from a specified source entity.
-
D.
sponsorBrandType
Indicates the type or category of brand that is acting as a sponsor in the relationship.
-
E.
sponsorProduct
Indicates that one entity financially supports or endorses a product, typically in exchange for promotion or association with that product.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 12:23 a.m.