Triple
T21859738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL 2002 |
E539727
|
entity |
| Predicate | hasRosterEra |
P37944
|
FINISHED |
| Object | early-2000s NHL rosters |
—
|
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: early-2000s NHL rosters | Statement: [NHL 2002, hasRosterEra, early-2000s NHL rosters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRosterEra Context triple: [NHL 2002, hasRosterEra, early-2000s NHL rosters]
-
A.
playedWithEra
Indicates that an entity performed or was active during a specified historical or stylistic era.
-
B.
refersToEraOfCareer
chosen
Indicates that one entity specifies or denotes the particular era or phase within another entity’s career.
-
C.
associatedWithPlayerEra
Indicates a relationship where something is linked or connected to a specific era or period in a player's career.
-
D.
notableLeagueEra
Indicates that the subject is significantly associated with, or best known for participating in, a particular era or period of a sports league.
-
E.
hasRetiredPlayersFrom
Indicates that an entity has players who previously played for it and have since retired, originating from the specified source entity (e.g., team, league, or country).
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63944d88190b6bd5e6ba4cc8ec1 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.