Triple
T32069279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust-eze Racing |
E818966
|
entity |
| Predicate | sponsorLogoFeatures |
P10231
|
FINISHED |
| Object | Rust-eze wordmark |
—
|
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: Rust-eze wordmark | Statement: [Rust-eze Racing, sponsorLogoFeatures, Rust-eze wordmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorLogoFeatures Context triple: [Rust-eze Racing, sponsorLogoFeatures, Rust-eze wordmark]
-
A.
logoFeature
chosen
Indicates that an entity serves as a distinctive visual element or component within a logo.
-
B.
sponsorBrandType
Indicates the type or category of brand that is acting as a sponsor in the relationship.
-
C.
sponsorshipBrand
Indicates that one entity serves as a sponsoring brand for another entity, typically providing support, funding, or endorsement.
-
D.
logoUsedBy
Indicates that a particular logo is employed or displayed by a specific entity as part of its identity, branding, or representation.
-
E.
logoOwner
Indicates that one entity is the owner or rights holder of another entity’s logo.
- 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:23 a.m.