Triple
T21629227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Community Shield |
E533783
|
entity |
| Predicate | goalsBenefit |
P487
|
FINISHED |
| Object | charitable and community causes historically |
—
|
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: charitable and community causes historically | Statement: [FA Community Shield, goalsBenefit, charitable and community causes historically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalsBenefit Context triple: [FA Community Shield, goalsBenefit, charitable and community causes historically]
-
A.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
benefits
chosen
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
D.
benefice
Indicates that one entity grants or bestows a benefit, favor, or advantage upon another.
-
E.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another 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.