Triple
T24194129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2004–05 |
E599781
|
entity |
| Predicate | championsGoalsConceded |
P51307
|
FINISHED |
| Object | Chelsea F.C. conceded 15 league goals |
—
|
NE NERFINISHED |
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: Chelsea F.C. conceded 15 league goals | Statement: [Premier League 2004–05, championsGoalsConceded, Chelsea F.C. conceded 15 league goals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championsGoalsConceded Context triple: [Premier League 2004–05, championsGoalsConceded, Chelsea F.C. conceded 15 league goals]
-
A.
championsGoalsFor
Indicates that an entity actively supports, advocates for, or works to advance the goals of another entity.
-
B.
championsGoalAverage
Indicates the average number of goals scored (or conceded) by a champion over a defined set of games or season.
-
C.
goalsConceded
Indicates the number of goals a team or player has allowed the opposing side to score.
-
D.
leagueGoalsAgainst
chosen
Indicates the number of goals a team has conceded in league competition against its opponents.
-
E.
numberOfGoals
Indicates the total count of goals scored or achieved by an entity in a given 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24947948190b609a39a2b8828ad |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.