Triple
T7598979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ice Blast |
E179931
|
entity |
| Predicate | sponsorFrom |
P78081
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Ice Blast, sponsorFrom, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorFrom Context triple: [Ice Blast, sponsorFrom, 1997]
-
A.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
-
B.
sponsorEnd
Indicates the point in time or condition at which a sponsorship relationship or sponsorship-related action comes to an end.
-
C.
sponsorType
Indicates the specific role or category of sponsorship that an entity provides in relation to another entity or event.
-
D.
sponsorAssociatedWith
Indicates a relationship where a sponsor is connected to, involved with, or responsible for supporting another entity.
-
E.
sponsorField
Indicates that one entity acts as a sponsor specifically in the context of a particular field, domain, or area associated with another entity.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d67cf88190a3202c07f7cea7df |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:53 p.m.