Triple
T11383095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Red Wings–Chicago Black Hawks rivalry |
E269646
|
entity |
| Predicate | teamDivisionContext |
P41042
|
FINISHED |
| Object | Central Division era |
—
|
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: Central Division era | Statement: [Detroit Red Wings–Chicago Black Hawks rivalry, teamDivisionContext, Central Division era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamDivisionContext Context triple: [Detroit Red Wings–Chicago Black Hawks rivalry, teamDivisionContext, Central Division era]
-
A.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
-
B.
team1Division
chosen
Indicates the competitive division or grouping in which the first team participates or is classified.
-
C.
teamDivisionControlled
Indicates that one entity has authority over or manages the organizational structure or division of a team.
-
D.
gameDivision
Indicates a hierarchical or categorical separation of a game into distinct parts, sections, or groups.
-
E.
makerDivision
Indicates that one entity is a specific division or subdivision within the organization or structure of the entity that created or produced another entity.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.