Triple
T36109704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Browns |
E1044458
|
entity |
| Predicate | reestablishedAsExpansionTeam |
P905
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Cleveland Browns, reestablishedAsExpansionTeam, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reestablishedAsExpansionTeam Context triple: [Cleveland Browns, reestablishedAsExpansionTeam, 1999]
-
A.
joinedLeagueAsExpansionTeamWith
Indicates that an entity entered a league as a newly created expansion team together with another specified entity.
-
B.
foundedAsExpansionTeamOf
Indicates that an organization or team was originally established as a new expansion unit of another existing organization or league.
-
C.
expansionTeamIn
chosen
Indicates that a sports team entered a league or competition as an expansion team in a specified season, year, or context.
-
D.
expansionTeamWith
Indicates that one entity is an expansion team associated with, or added to, another entity such as a league, division, or organization.
-
E.
expandedFromTeams
Indicates that something has been enlarged, extended, or developed starting from one or more teams as the original basis.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.