Triple
T30487829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Britain Bees |
E775768
|
entity |
| Predicate | replacedTeamInCity |
P160069
|
FINISHED |
| Object | New Britain Rock Cats |
—
|
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: New Britain Rock Cats | Statement: [New Britain Bees, replacedTeamInCity, New Britain Rock Cats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedTeamInCity Context triple: [New Britain Bees, replacedTeamInCity, New Britain Rock Cats]
-
A.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
B.
replacedStadiumForTeam
Indicates that one stadium succeeded and took over the role of another as the home venue for a particular team.
-
C.
formerHomeTeamReplaced
chosen
Indicates that one team previously played its home games at a venue but was later replaced there by another team.
-
D.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
E.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 29, 2026, 8:13 p.m.