Triple
T24663503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL 100 Greatest Players list |
E610603
|
entity |
| Predicate | notablePlayerIncluded |
P9730
|
FINISHED |
| Object | Mario Lemieux |
—
|
NE NERFINISHED |
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: Mario Lemieux | Statement: [NHL 100 Greatest Players list, notablePlayerIncluded, Mario Lemieux]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerIncluded Context triple: [NHL 100 Greatest Players list, notablePlayerIncluded, Mario Lemieux]
-
A.
hasNotablePlayer
chosen
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
-
B.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
C.
notablePlayerInFinal
Indicates that a player had a significant or standout role in the final match or game of a competition.
-
D.
notableTeammate
Indicates that one entity has a teammate relationship with another entity who is particularly prominent, distinguished, or noteworthy.
-
E.
notableBowlParticipant
Indicates that an entity has participated in a bowl game in a way considered notable or significant.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 2:34 a.m.