Triple
T218122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League |
E4152
|
entity |
| Predicate | matchPointsDraw |
P8178
|
FINISHED |
| Object | 1 |
—
|
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 | Statement: [Premier League, matchPointsDraw, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchPointsDraw Context triple: [Premier League, matchPointsDraw, 1]
-
A.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
B.
isRematchOfFinal
Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
-
C.
majorChallenger
Indicates that one entity is a primary competitor or leading rival to another in a given context or domain.
-
D.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
-
E.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5062e48190833be10e4770e1e9 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25be349588190aedde33d80682344 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.