Triple
T36019718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris DiDomenico |
E1041947
|
entity |
| Predicate | notableLeagueExperience |
P71658
|
FINISHED |
| Object | NHL |
E1381
|
NE 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 | Statement: [Chris DiDomenico, notableLeagueExperience, NHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLeagueExperience Context triple: [Chris DiDomenico, notableLeagueExperience, NHL]
-
A.
hasExperienceInLeague
chosen
Indicates that an entity has previously participated or been involved in a particular league.
-
B.
notableLeague
Indicates that there is a significant or prominent league associated with the subject entity.
-
C.
notableLeagueScope
Indicates that the relationship or action pertains to the scope or level (e.g., local, national, international) of a league in which an entity is notably involved or recognized.
-
D.
hasProfessionalLeague
Indicates that an entity is associated with or participates in a recognized professional sports league.
-
E.
hasSeniorClubExperience
Indicates that an individual has played for or been a member of a senior-level (adult/professional) sports club.
- F. None of above.
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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38c00029e48190a3fc0ba33c25f6ba |
completed | June 22, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.