Triple
T34027127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fredericton Canadiens |
E872538
|
entity |
| Predicate | formerTeamStatus |
P201425
|
FINISHED |
| Object | defunct |
—
|
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: defunct | Statement: [Fredericton Canadiens, formerTeamStatus, defunct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTeamStatus Context triple: [Fredericton Canadiens, formerTeamStatus, defunct]
-
A.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
-
B.
officialStatusWithTeam
Indicates that an entity holds or has held an official role, position, or status in relation to a specific team.
-
C.
hasFormerTeam
Indicates that an entity was previously a member of, played for, or was affiliated with a team in the past but is no longer associated with that team.
-
D.
formerLeagueTeam
Indicates that an entity was previously a member team of a particular sports league but is no longer part of that league.
-
E.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
- F. None of above. chosen
Provenance (4 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fff4525ce48190b1d760539e68aadc |
completed | May 10, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:51 a.m.