Triple
T22289131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheffield derby |
E550944
|
entity |
| Predicate | typicalKickoffType |
P147937
|
FINISHED |
| Object | league match |
—
|
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: league match | Statement: [Sheffield derby, typicalKickoffType, league match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalKickoffType Context triple: [Sheffield derby, typicalKickoffType, league match]
-
A.
typicalKickoffSlot
Indicates the usual or standard time slot when a kickoff event (such as a game or meeting) is scheduled to begin.
-
B.
kickingStyle
Indicates the manner or technique with which an entity performs a kicking action in a given context.
-
C.
typeOfFootball
Indicates the specific code or variant of football that characterizes or classifies a given football-related entity.
-
D.
kickingTeam
Indicates which team is performing the kick in a play or event.
-
E.
gameWinningKicker
Indicates that an entity serves as the kicker responsible for securing the decisive, game-winning score in a contest.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15609854c81908adb7681cff2c404 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e75dc7b08081909d64441e979c2fa4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 8:41 p.m.