Triple
T16376191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI rainbow jersey |
E397684
|
entity |
| Predicate | sponsorPlacement |
P123155
|
FINISHED |
| Object | team sponsor logos allowed |
—
|
LITERAL 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: team sponsor logos allowed | Statement: [UCI rainbow jersey, sponsorPlacement, team sponsor logos allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorPlacement Context triple: [UCI rainbow jersey, sponsorPlacement, team sponsor logos allowed]
-
A.
sponsorEnd
Indicates the point in time or condition at which a sponsorship relationship or sponsorship-related action comes to an end.
-
B.
sponsorPosition
Indicates that one entity financially or otherwise supports another entity in holding or obtaining a particular position, role, or placement.
-
C.
sponsorFrom
Indicates that one entity provides sponsorship or financial backing originating from a specified source entity.
-
D.
sponsorProduct
Indicates that one entity financially supports or endorses a product, typically in exchange for promotion or association with that product.
-
E.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
- F. None of above. chosen
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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319d79df8819087285b9457b7bdb6 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.