Triple
T34987415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brendan Connolly |
E1008989
|
entity |
| Predicate | leagueExperience |
P71658
|
FINISHED |
| Object | Elite Ice Hockey League |
—
|
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: Elite Ice Hockey League | Statement: [Brendan Connolly, leagueExperience, Elite Ice Hockey League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueExperience Context triple: [Brendan Connolly, leagueExperience, Elite Ice Hockey League]
-
A.
hasExperienceInLeague
chosen
Indicates that an entity has previously participated or been involved in a particular league.
-
B.
leagueContext
Indicates the broader league or competition setting within which the relationship or action takes place.
-
C.
hasSeniorClubExperience
Indicates that an individual has played for or been a member of a senior-level (adult/professional) sports club.
-
D.
leagueHonour
Indicates that an entity has received a specific honour, award, or title associated with a sports league or competitive league organization.
-
E.
commandExperience
Indicates that an entity has experience or a track record in holding command or leadership roles over others.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.