Triple
T7594763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL First All-Star Team |
E179828
|
entity |
| Predicate | isNonPlayingHonor |
P28153
|
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: [NHL First All-Star Team, isNonPlayingHonor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonPlayingHonor Context triple: [NHL First All-Star Team, isNonPlayingHonor, true]
-
A.
isNonPlayingAward
chosen
Indicates that an award is given for contributions not involving active participation in the game or performance itself.
-
B.
honoursAsPlayer
Indicates that one entity has received awards, recognitions, or honours specifically for their role or achievements as a player.
-
C.
isPlayerAward
Indicates that an award is designated specifically for a player, representing a recognition or honor given to an individual participant.
-
D.
honorsRoleAs
Indicates that one entity shows respect, recognition, or deference to another entity specifically in their official position or function.
-
E.
isCivilianHonourGrade
Indicates that one entity is classified as a specific grade or level within a system of civilian honours or awards in relation to 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9bbcd8081909a229d7faa2ffdc8 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.