Triple
T21629228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Community Shield |
E533783
|
entity |
| Predicate | typicalKickoff |
P51718
|
FINISHED |
| Object | pre-season period |
—
|
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: pre-season period | Statement: [FA Community Shield, typicalKickoff, pre-season period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalKickoff Context triple: [FA Community Shield, typicalKickoff, pre-season period]
-
A.
typicalKickoffSlot
chosen
Indicates the usual or standard time slot when a kickoff event (such as a game or meeting) is scheduled to begin.
-
B.
kickingTeam
Indicates which team is performing the kick in a play or event.
-
C.
kicker
Indicates that an entity performs the action of kicking another entity, typically in a sports or physical interaction context.
-
D.
gameWinningKicker
Indicates that an entity serves as the kicker responsible for securing the decisive, game-winning score in a contest.
-
E.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5215ae3c81909e6dedba23822970 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.