Triple
T8830457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Gladiators |
E210123
|
entity |
| Predicate | 2014Achievement |
P69742
|
FINISHED |
| Object | American Conference champions |
—
|
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: American Conference champions | Statement: [Cleveland Gladiators, 2014Achievement, American Conference champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2014Achievement Context triple: [Cleveland Gladiators, 2014Achievement, American Conference champions]
-
A.
2014Winner
chosen
Indicates that the subject is the winner of a specified competition, award, or event that took place in the year 2014.
-
B.
associatedAchievement
Indicates a relationship where one entity is linked to, or recognized in connection with, a particular achievement.
-
C.
achievementDefinition
Indicates that one entity specifies or defines the criteria, properties, or structure of an achievement associated with another entity.
-
D.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
E.
awardGivenAt
Indicates that an award was conferred at a specific event, location, or occasion.
- 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.