Triple
T27932519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017–18 Serie A |
E708019
|
entity |
| Predicate | titleDecidedOnFinalMatchday |
P155127
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2017–18 Serie A, titleDecidedOnFinalMatchday, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleDecidedOnFinalMatchday Context triple: [2017–18 Serie A, titleDecidedOnFinalMatchday, true]
-
A.
titleDecidedOnFinalDay
chosen
Indicates that the outcome determining the title or championship was only decided on the final day of the relevant competition or period.
-
B.
finalMatchDecidedBy
Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
-
C.
titleDecidingMatch
Indicates a match whose outcome determines the winner of a title or championship.
-
D.
titleDecidedOn
Indicates that a final decision has been made regarding the title assigned to an entity or work.
-
E.
finalMatchDetermines
Indicates that the outcome of a final match decides or establishes a particular result, status, or consequence for the related entities.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 27, 2026, 7:03 p.m.