Triple
T13282465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Staleys |
E316356
|
entity |
| Predicate | successorLeagueTeam |
P30650
|
FINISHED |
| Object | Chicago Bears in the NFL |
—
|
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: Chicago Bears in the NFL | Statement: [Chicago Staleys, successorLeagueTeam, Chicago Bears in the NFL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLeagueTeam Context triple: [Chicago Staleys, successorLeagueTeam, Chicago Bears in the NFL]
-
A.
successorTeamLeague
chosen
Indicates that one sports league is the direct successor to another for a given team’s participation or affiliation.
-
B.
successorTeamFranchise
Indicates that one team franchise is the direct successor or continuation of another team franchise, typically following relocation, renaming, or reorganization.
-
C.
successorTeamInCity
Indicates that one team is the direct replacement or continuation of another team within the same city.
-
D.
successorLeagueInMarket
Indicates that one league has replaced another as the primary league operating in a given market.
-
E.
homeTeamCurrentSuccessor
Indicates that one team is the immediate next home team in a sequence of home-team assignments or events.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.