Triple
T24357373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAFC |
E613959
|
entity |
| Predicate | introducedFranchiseToNFL |
P39326
|
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: [AAFC, introducedFranchiseToNFL, Cleveland Browns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedFranchiseToNFL Context triple: [AAFC, introducedFranchiseToNFL, Cleveland Browns]
-
A.
mergedIntoNFL
chosen
Indicates that an organization or league ceased to exist independently by being absorbed and incorporated into the National Football League (NFL).
-
B.
franchiseFirstSuperBowlWin
Indicates the specific Super Bowl game in which a franchise achieved its first-ever championship victory.
-
C.
hasHistoricNFLFranchise
Indicates that a location or entity has been home to an NFL franchise that existed in the past, whether or not that franchise is still active or located there.
-
D.
playedForNFLTeam
Indicates that a person was a member of and played for a specific NFL team.
-
E.
beganWithFranchise
Indicates that an entity originated or started as part of a particular 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_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. |
Created at: April 18, 2026, 2 a.m.