Triple
T21629233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Community Shield |
E533783
|
entity |
| Predicate | deciderFor |
P145296
|
FINISHED |
| Object | English season-opening honour |
—
|
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: English season-opening honour | Statement: [FA Community Shield, deciderFor, English season-opening honour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deciderFor Context triple: [FA Community Shield, deciderFor, English season-opening honour]
-
A.
deciderOf
Indicates that one entity is the one who makes decisions or choices regarding another entity or situation.
-
B.
decider
Indicates that an entity is the one who makes a choice or decision in a given situation or process.
-
C.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
D.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
E.
deciderFormat
Indicates the format or representation in which a decision or choice is expressed or encoded.
- 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_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. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:34 p.m.