Triple
T34624762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division III Directors' Cup |
E889103
|
entity |
| Predicate | firstSponsor |
P146741
|
FINISHED |
| Object | Sears |
E17326
|
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: Sears | Statement: [Division III Directors' Cup, firstSponsor, Sears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSponsor Context triple: [Division III Directors' Cup, firstSponsor, Sears]
-
A.
originalSponsor
Indicates that one entity is the initial or primary sponsor responsible for supporting, funding, or backing another entity or activity.
-
B.
formerSponsor
Indicates that an entity previously acted as a sponsor for another entity but no longer holds that sponsoring role.
-
C.
firstYearTitleSponsor
chosen
Indicates that the entity served as the title sponsor for the first year of a particular event, program, or competition.
-
D.
hasSponsor
Indicates that one entity financially or otherwise supports another entity, typically in exchange for recognition or other benefits.
-
E.
previousSponsor
Indicates that an entity formerly acted as a sponsor for another entity at some earlier time but no longer does so.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37411f78988190bcd482dc44a63df7 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.