Triple
T22665504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2012–13 |
E559771
|
entity |
| Predicate | ManchesterCityPoints |
P149147
|
FINISHED |
| Object | 78 |
—
|
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: 78 | Statement: [Premier League 2012–13, ManchesterCityPoints, 78]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ManchesterCityPoints Context triple: [Premier League 2012–13, ManchesterCityPoints, 78]
-
A.
goalsForManchesterCity
Indicates the number of goals that were scored for Manchester City.
-
B.
ManchesterUnitedScore
Indicates that the event or situation involves Manchester United scoring a goal or achieving a specific number of goals.
-
C.
premierLeagueGoalsForManchesterCity
Indicates the number of goals a player has scored for Manchester City in Premier League matches.
-
D.
cityFootballContext
Indicates a contextual relationship where an event, action, or entity is specifically situated within the domain of football as it relates to a particular city (e.g., its clubs, matches, or local football culture).
-
E.
ChelseaManager
Indicates that a person holds or has held the position of manager (head coach) of Chelsea Football Club.
- 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.