Triple
T614009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Community Shield |
E12162
|
entity |
| Predicate | seasonRole |
P14881
|
FINISHED |
| Object | English football season curtain-raiser |
—
|
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 football season curtain-raiser | Statement: [FA Community Shield, seasonRole, English football season curtain-raiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRole Context triple: [FA Community Shield, seasonRole, English football season curtain-raiser]
-
A.
seasonCharacterization
chosen
Indicates how a particular season is described, defined, or characterized in terms of its qualities or attributes.
-
B.
season
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
-
C.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
popularSeason
Indicates that a particular season is widely liked, favored, or frequently chosen by many people.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e0a0f588190b953fdb585263307 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.