Triple
T32069248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust-eze |
E818965
|
entity |
| Predicate | sponsorOfEvent |
P78082
|
FINISHED |
| Object | Piston Cup |
—
|
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: Piston Cup | Statement: [Rust-eze, sponsorOfEvent, Piston Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorOfEvent Context triple: [Rust-eze, sponsorOfEvent, Piston Cup]
-
A.
coSponsor
Indicates that an entity jointly supports, endorses, or backs an initiative, proposal, or activity together with one or more others.
-
B.
sponsorParty
Indicates that one party provides support, typically financial or promotional, to another party, often in exchange for association or visibility.
-
C.
sponsorTo
chosen
Indicates that one entity provides support, funding, or endorsement to another entity, typically to enable or promote the latter’s activities or initiatives.
-
D.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
-
E.
sponsorAtWorldsFair
Indicates that an entity serves as a sponsor or patron for something (such as an exhibit, event, or participant) at a World's Fair.
- 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_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 12:23 a.m.