Triple
T8830443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Gladiators |
E210123
|
entity |
| Predicate | relocationYearToCleveland |
P63822
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Cleveland Gladiators, relocationYearToCleveland, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationYearToCleveland Context triple: [Cleveland Gladiators, relocationYearToCleveland, 2008]
-
A.
relocationYear
Indicates the year in which an entity was moved or transferred from one location to another.
-
B.
relocatedToTokyoDomeYear
Indicates the year in which an entity moved or was transferred to Tokyo Dome.
-
C.
teamRelocationYear
chosen
Indicates the year in which a team moved from one location to another.
-
D.
originalBrownsRelocationYear
Indicates the year in which the original Browns franchise relocated from its original city to a new location.
-
E.
team2RelocationYear
Indicates the year in which the second team in a relationship was relocated to a different place or franchise.
- 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_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. |
Created at: March 30, 2026, 6:47 p.m.