Triple
T23814615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Goodwood Festival |
E589059
|
entity |
| Predicate | sponsorshipNameInUseFrom |
P40278
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Qatar Goodwood Festival, sponsorshipNameInUseFrom, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipNameInUseFrom Context triple: [Qatar Goodwood Festival, sponsorshipNameInUseFrom, 2015]
-
A.
sponsorshipNameSince
chosen
Indicates the date or time from which a particular sponsorship name has been in effect for the associated entity or relationship.
-
B.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
C.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
D.
sponsorshipNameAdopted
Indicates that an entity has adopted or taken on a specific sponsorship name as its official or recognized designation.
-
E.
previousSponsorshipName
Indicates that an entity had a different sponsorship name in the past, specifying what that prior sponsored name was.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7a9ce708190a27195d58589d757 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:57 p.m.