Triple
T24580147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby League World Cup 9s |
E608224
|
entity |
| Predicate | sponsor2019 |
P1807
|
FINISHED |
| Object | Downer |
—
|
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: Downer | Statement: [Rugby League World Cup 9s, sponsor2019, Downer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsor2019 Context triple: [Rugby League World Cup 9s, sponsor2019, Downer]
-
A.
sponsors
chosen
Indicates that one entity provides financial or material support to another, often in exchange for association, promotion, or fulfillment of certain activities or goals.
-
B.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
-
C.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
D.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
E.
sponsorEnd
Indicates the point in time or condition at which a sponsorship relationship or sponsorship-related action comes to an end.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a97fde9c81909d8de91b6358a015 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.