Triple
T30682182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014–15 Premier League season |
E781082
|
entity |
| Predicate | titleClinchedMatchScore |
P144175
|
FINISHED |
| Object | 1–0 |
—
|
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: 1–0 | Statement: [2014–15 Premier League season, titleClinchedMatchScore, 1–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleClinchedMatchScore Context triple: [2014–15 Premier League season, titleClinchedMatchScore, 1–0]
-
A.
clinchingScore
Indicates the score or point threshold at which a participant secures a decisive or unassailable victory in a competition or contest.
-
B.
titleClinchedRoundsRemaining
Indicates the number of rounds remaining in a competition or season at the point when a title or championship has been mathematically secured.
-
C.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
D.
clinchSeries
Indicates that one competitor secures the decisive victory needed to win an entire series or matchup.
-
E.
titleGameScore
chosen
Indicates the score or result achieved in a specific game or match associated with a title or competition.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 29, 2026, 8:33 p.m.