Triple
T28384323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Ulster Cup |
E718979
|
entity |
| Predicate | finalUsuallyPlayedOn |
P184362
|
FINISHED |
| Object | Boxing Day |
—
|
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: Boxing Day | Statement: [Mid-Ulster Cup, finalUsuallyPlayedOn, Boxing Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalUsuallyPlayedOn Context triple: [Mid-Ulster Cup, finalUsuallyPlayedOn, Boxing Day]
-
A.
finalUsuallyPlayedIn
Indicates that an event or competition’s final round is typically held in a particular location or venue.
-
B.
finalPlayedIn
Indicates that an entity participated in the final match or round of a competition or tournament in a specified context.
-
C.
laterPlayedWith
Indicates that one entity engaged in play with another entity at a later time than some referenced or implied earlier event.
-
D.
isOftenPlayedFor
Indicates that one entity is frequently performed, used, or presented for the benefit, enjoyment, or experience of another entity.
-
E.
lastGamePlayed
Indicates the most recent game that an entity has participated in or played.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 28, 2026, 1:08 a.m.