Triple
T33881589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binghamton Devils |
E868504
|
entity |
| Predicate | successorTeamInBinghamton |
P45971
|
FINISHED |
| Object | Binghamton Black Bears |
—
|
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: Binghamton Black Bears | Statement: [Binghamton Devils, successorTeamInBinghamton, Binghamton Black Bears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTeamInBinghamton Context triple: [Binghamton Devils, successorTeamInBinghamton, Binghamton Black Bears]
-
A.
successorTeamAbbreviation
Indicates that one team, identified by its abbreviation, is the successor or replacement of another team, also identified by its abbreviation.
-
B.
successorTeamInCity
chosen
Indicates that one team is the direct replacement or continuation of another team within the same city.
-
C.
successorTeamFranchise
Indicates that one team franchise is the direct successor or continuation of another team franchise, typically following relocation, renaming, or reorganization.
-
D.
successorTeamInWashington
Indicates that one team is the direct successor to another team that was previously based in Washington.
-
E.
successorTeamLocation
Indicates that one team location directly follows or replaces another team location in a sequence or organizational lineage.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
Created at: May 1, 2026, 1:48 a.m.