Triple
T5585286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL Championship under-21 team |
E146739
|
entity |
| Predicate | typicalMatchDay |
P64902
|
FINISHED |
| Object | reduced attendance compared to first team |
—
|
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: reduced attendance compared to first team | Statement: [EFL Championship under-21 team, typicalMatchDay, reduced attendance compared to first team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMatchDay Context triple: [EFL Championship under-21 team, typicalMatchDay, reduced attendance compared to first team]
-
A.
matchdayActivity
Indicates the specific activity, event, or engagement that takes place in connection with a particular match day.
-
B.
mostCommonMatchDay
Indicates the day of the week on which matches most frequently occur for a given set of matches or competition.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
matchdayLocation
Indicates the venue or place where a particular matchday or game is held.
-
E.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02085d0e48190b8d185fe7f3d8579 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:38 p.m.