Triple
T22665502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2012–13 |
E559771
|
entity |
| Predicate | ManchesterUnitedTitleConfirmedDate |
P149145
|
FINISHED |
| Object | 2013-04-22 |
—
|
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: 2013-04-22 | Statement: [Premier League 2012–13, ManchesterUnitedTitleConfirmedDate, 2013-04-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ManchesterUnitedTitleConfirmedDate Context triple: [Premier League 2012–13, ManchesterUnitedTitleConfirmedDate, 2013-04-22]
-
A.
joinedManchesterUnited
Indicates that an entity became a member of, or signed to play for, Manchester United.
-
B.
ManchesterUnitedDivision
Indicates that an entity is a competitive division or league level in which Manchester United participates or has participated.
-
C.
ManchesterUnitedScore
Indicates that the event or situation involves Manchester United scoring a goal or achieving a specific number of goals.
-
D.
leftManchesterUnited
Indicates that an entity departed from or is no longer a member of Manchester United.
-
E.
leagueTitlesWonWithManchesterUnited
Indicates the number of league titles an entity has won while playing for or managing Manchester United.
- 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.