Triple
T28005231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League season (August–May) |
E707257
|
entity |
| Predicate | tableBasis |
P163617
|
FINISHED |
| Object | total points |
—
|
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: total points | Statement: [Premier League season (August–May), tableBasis, total points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tableBasis Context triple: [Premier League season (August–May), tableBasis, total points]
-
A.
tableType
Indicates the specific category or kind of table that an entity is classified as.
-
B.
tableSetting
Indicates the arrangement and placement of items (such as dishes, utensils, and glasses) prepared on a table for a meal.
-
C.
tableName
Indicates the name assigned to a database table that participates in the described relationship or operation.
-
D.
titleBasis
Indicates that one entity serves as the basis or source material for the title or name of another entity.
-
E.
formsBasis
Indicates that one entity serves as the foundational support, justification, or underlying principle upon which another entity is built, derived, or depends.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bd4e25c81909b4a26577a4a5479 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 7:59 p.m.