Triple
T36532248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberdeen IronBirds |
E900475
|
entity |
| Predicate | previousNameOfFranchise |
P77043
|
FINISHED |
| Object | Utica Blue Sox |
—
|
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: Utica Blue Sox | Statement: [Aberdeen IronBirds, previousNameOfFranchise, Utica Blue Sox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNameOfFranchise Context triple: [Aberdeen IronBirds, previousNameOfFranchise, Utica Blue Sox]
-
A.
previousFranchiseName
chosen
Indicates that an entity previously operated under a different franchise name, specifying what that earlier franchise name was.
-
B.
franchiseRenamedAs
Indicates that an existing franchise has changed its official name to a new one.
-
C.
formerFranchise
Indicates that an entity previously held a franchise relationship with another entity but no longer does.
-
D.
previousFranchise
Indicates that one franchise directly precedes another in a series or succession of related franchises.
-
E.
previousFranchiseTitleYear
Indicates the year in which the immediately preceding title in the same franchise was released.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:11 p.m.