Triple
T384662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Penguins |
E8753
|
entity |
| Predicate | expansionTeamOf |
P905
|
FINISHED |
| Object | 1967 NHL expansion |
—
|
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: 1967 NHL expansion | Statement: [Pittsburgh Penguins, expansionTeamOf, 1967 NHL expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionTeamOf Context triple: [Pittsburgh Penguins, expansionTeamOf, 1967 NHL expansion]
-
A.
expansionTeamIn
chosen
Indicates that a sports team entered a league or competition as an expansion team in a specified season, year, or context.
-
B.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
C.
team1Franchise
Indicates that an entity serves as or represents the franchise associated with the first team in a given sports or competitive context.
-
D.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
-
E.
team2Franchise
Indicates a relationship where a second team is associated with, or belongs to, a particular franchise.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec422b808190b6ddf747ef939151 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.