Triple
T8270426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 NHL All-Star Game |
E193412
|
entity |
| Predicate | featuresTopPlayersOfLeague |
P5844
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1995 NHL All-Star Game, featuresTopPlayersOfLeague, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTopPlayersOfLeague Context triple: [1995 NHL All-Star Game, featuresTopPlayersOfLeague, true]
-
A.
featuresTopPlayers
Indicates that something prominently presents or showcases the most outstanding or highly ranked players.
-
B.
featuresTopPlayersFrom
chosen
Indicates that something includes or showcases the most prominent or best-performing players from a specified source or group.
-
C.
topScorer
Indicates that the subject is the individual with the highest score among a specified group or in a particular context.
-
D.
leagueLeader
Indicates that the subject entity is currently ranked first or holds the top position within a specified league or competitive grouping.
-
E.
leagueLeaderIn
Indicates that an entity is the current top-ranked or leading participant within a specified league or competition.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb795243fc8190a66afef7476e1147 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:50 p.m.