Triple
T24357471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Division (AAFC) |
E613962
|
entity |
| Predicate | hadChampionTeam |
P155910
|
FINISHED |
| Object | Cleveland Browns |
—
|
NE NERFINISHED |
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: Cleveland Browns | Statement: [Western Division (AAFC), hadChampionTeam, Cleveland Browns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadChampionTeam Context triple: [Western Division (AAFC), hadChampionTeam, Cleveland Browns]
-
A.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
B.
hasHeroTeam
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
-
C.
championQualifiedTeam
Indicates that a team has successfully qualified to participate in a championship competition.
-
D.
homeTeamChampion
Indicates that the team playing at home is the champion or title-holding team in the given context.
-
E.
hadTeamFromCountry
Indicates that an entity (such as an event, league, or competition) included or was associated with at least one team originating from a specified country.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29349ee188190a9d54b2c725b8a27 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2 a.m.