Triple
T18250066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsea 2004–05 Premier League title-winning season |
E437065
|
entity |
| Predicate | cleanSheets |
P131020
|
FINISHED |
| Object | 25 |
—
|
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: 25 | Statement: [Chelsea 2004–05 Premier League title-winning season, cleanSheets, 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleanSheets Context triple: [Chelsea 2004–05 Premier League title-winning season, cleanSheets, 25]
-
A.
cleaningAction
Indicates an action in which an agent removes dirt, impurities, or unwanted substances from a target object, area, or entity.
-
B.
clearingSystem
Indicates that one entity functions as the financial clearing mechanism or infrastructure used to settle transactions for another entity.
-
C.
cleaningProperty
Indicates that one entity serves as a cleaning-related attribute, method, or characteristic associated with another entity.
-
D.
sweep
Indicates that an agent uses a tool or motion to clear or move unwanted material from a surface or area.
-
E.
notCleanedFor
Indicates that one entity has not been cleaned, maintained, or cleared in preparation for use by another entity.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd8065b08190ae8d37102141f470 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:33 a.m.