Triple
T16320023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Most Exciting Two Minutes in Sports |
E396265
|
entity |
| Predicate | refersToEventHeld |
P122689
|
FINISHED |
| Object | annually |
—
|
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: annually | Statement: [The Most Exciting Two Minutes in Sports, refersToEventHeld, annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToEventHeld Context triple: [The Most Exciting Two Minutes in Sports, refersToEventHeld, annually]
-
A.
refersToEventType
Indicates that one entity references or is associated with a specific type or category of event.
-
B.
connectsToEventVenue
Indicates that one entity serves as a link or route providing access or connection to an event venue.
-
C.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
D.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
E.
associatedWithEventHost
Indicates that an entity has a relationship or connection with the host of a particular event.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b4ad448190b2b195a5e0032c6e |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.