Triple
T29901543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reading FC |
E759418
|
entity |
| Predicate | 2005–06PointsRecord |
P52800
|
FINISHED |
| Object | 106 points in the Championship |
—
|
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: 106 points in the Championship | Statement: [Reading FC, 2005–06PointsRecord, 106 points in the Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2005–06PointsRecord Context triple: [Reading FC, 2005–06PointsRecord, 106 points in the Championship]
-
A.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
B.
singleGamePointsRecordYear
Indicates the year in which a single-game points record was set.
-
C.
seasonPointsRecordSet
chosen
Indicates that a new record for total points scored in a season has been achieved or established.
-
D.
2011–12Record
Indicates the performance record or results achieved during the 2011–12 season.
-
E.
regularSeasonRecord2016
Indicates the win-loss (and possibly tie) performance of an entity during the 2016 regular season.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772ecd788190acfe7c583599b3c1 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:06 p.m.