Triple
T17173821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Sheffield and Dearne Athletic Club |
E416805
|
entity |
| Predicate | offersEventGroup |
P126374
|
FINISHED |
| Object | sprints |
—
|
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: sprints | Statement: [City of Sheffield and Dearne Athletic Club, offersEventGroup, sprints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersEventGroup Context triple: [City of Sheffield and Dearne Athletic Club, offersEventGroup, sprints]
-
A.
offersEvent
Indicates that an entity provides or makes available a specific event.
-
B.
offersActivity
Indicates that one entity provides or makes available a specific activity for another entity to participate in or use.
-
C.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
D.
offersEdition
Indicates that one entity provides or makes available a particular version or edition of another entity.
-
E.
offersSchedule
Indicates that one entity provides or makes available a specific schedule to another entity or for a particular purpose.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0b7c9c819082e503cb493d7e7b |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:37 a.m.