Triple
T27797488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2011–12 with Manchester City |
E702153
|
entity |
| Predicate | decisiveMatchDate |
P14672
|
FINISHED |
| Object | 2012-05-13 |
—
|
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: 2012-05-13 | Statement: [Premier League 2011–12 with Manchester City, decisiveMatchDate, 2012-05-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveMatchDate Context triple: [Premier League 2011–12 with Manchester City, decisiveMatchDate, 2012-05-13]
-
A.
finalMatchDate
chosen
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
-
B.
decisiveMatchOf
Indicates that one entity is a match for another in a way that determines or strongly influences a final outcome or decision.
-
C.
decisiveMatchAttendance
Indicates that an entity attends a match whose outcome is crucial or decisive, such as determining a championship, qualification, or elimination.
-
D.
finalMatchDecidedBy
Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
-
E.
finalRoundDate
Indicates the date on which the final round of an event, process, or competition takes place.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 5:32 p.m.