Triple
T34803047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Whalers |
E1003270
|
entity |
| Predicate | hasSuccessorTeamLocation |
P36799
|
FINISHED |
| Object | Plymouth, Michigan |
—
|
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: Plymouth, Michigan | Statement: [Detroit Whalers, hasSuccessorTeamLocation, Plymouth, Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorTeamLocation Context triple: [Detroit Whalers, hasSuccessorTeamLocation, Plymouth, Michigan]
-
A.
hasSuccessorTeam
Indicates that one team is the direct successor or continuation of another team, typically following rebranding, relocation, or organizational change.
-
B.
successorTeamLocation
chosen
Indicates that one team location directly follows or replaces another team location in a sequence or organizational lineage.
-
C.
hasNoSuccessorTeam
Indicates that an entity (typically a team) does not have any subsequent or replacement team continuing its role, identity, or lineage.
-
D.
successorIncludesTeam
Indicates that a successor entity encompasses or retains the same team as (or a team derived from) the referenced entity.
-
E.
successorTeamAtBallpark
Indicates that one team is the direct successor of another as the primary tenant or home team at a particular ballpark.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: May 3, 2026, 3:59 p.m.