Triple
T17933517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betfair Chase |
E448392
|
entity |
| Predicate | hasSponsorSinceInauguration |
P129773
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Betfair Chase, hasSponsorSinceInauguration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSponsorSinceInauguration Context triple: [Betfair Chase, hasSponsorSinceInauguration, true]
-
A.
hasSponsor
Indicates that one entity financially or otherwise supports another entity, typically in exchange for recognition or other benefits.
-
B.
inauguratedBefore
Indicates that one entity’s inauguration occurred earlier in time than another entity’s inauguration.
-
C.
sponsorshipNameSince
Indicates the date or time from which a particular sponsorship name has been in effect for the associated entity or relationship.
-
D.
sponsorshipEra
Indicates the time period during which a sponsorship relationship is in effect between parties.
-
E.
hasInaugurationDate
Indicates the date on which an entity (such as an office, building, or position) was formally inaugurated or officially begun.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a5547b7881909dc41bb7dd34194f |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.