Triple
T22665505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2012–13 |
E559771
|
entity |
| Predicate | ChelseaPoints |
P149148
|
FINISHED |
| Object | 75 |
—
|
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: 75 | Statement: [Premier League 2012–13, ChelseaPoints, 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChelseaPoints Context triple: [Premier League 2012–13, ChelseaPoints, 75]
-
A.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
B.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
C.
pointsToWinSet
Indicates the number of points a player or side must win to secure the current set.
-
D.
challengerClub
Indicates that one club is the challenger or opposing club in a competitive context relative to another entity.
-
E.
points
Indicates that one entity directs attention, focus, or a physical/abstract indication toward another entity or location.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781b3dbc8190a312843cf8c1bfc6 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:08 p.m.