Triple
T21859725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL 2002 |
E539727
|
entity |
| Predicate | featuresPlayers |
P145955
|
FINISHED |
| Object | NHL players |
—
|
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: NHL players | Statement: [NHL 2002, featuresPlayers, NHL players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPlayers Context triple: [NHL 2002, featuresPlayers, NHL players]
-
A.
featuresPlayer
Indicates that something includes or prominently presents a particular player as part of its content or composition.
-
B.
featuresPlayersFrom
Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
-
C.
featuresTopPlayersFrom
Indicates that something includes or showcases the most prominent or best-performing players from a specified source or group.
-
D.
featuresTopPlayers
Indicates that something prominently presents or showcases the most outstanding or highly ranked players.
-
E.
recommendedPlayers
Indicates the suggested or optimal number of players that should participate in an activity or game.
- 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_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. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:56 p.m.