Triple
T8830456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Gladiators |
E210123
|
entity |
| Predicate | 2014Record |
P84888
|
FINISHED |
| Object | 17–1 regular season |
—
|
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: 17–1 regular season | Statement: [Cleveland Gladiators, 2014Record, 17–1 regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2014Record Context triple: [Cleveland Gladiators, 2014Record, 17–1 regular season]
-
A.
laterRecordedBy
Indicates that the subject work or version was recorded at a later time by the specified artist or entity.
-
B.
recordingYear
Indicates the specific calendar year in which something (such as audio, video, or data) was recorded.
-
C.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
D.
yearOfReference
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
-
E.
reRecordedReleaseYear
Indicates the year in which an existing work was recorded again and that re-recorded version was released.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc604db0788190a3082467d80fdaf5 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:47 p.m.