Triple
T30485940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild |
E775720
|
entity |
| Predicate | leagueLevelAssociation |
P50168
|
FINISHED |
| Object | National 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: National Hockey League | Statement: [Wild, leagueLevelAssociation, National Hockey League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueLevelAssociation Context triple: [Wild, leagueLevelAssociation, National Hockey League]
-
A.
associatedLeagueLevel
chosen
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
B.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
C.
athleticAssociationTier
Indicates the competitive level or division within an athletic association to which an entity (such as a team or institution) belongs.
-
D.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
E.
leagueAssociations
Indicates a relationship where an entity is formally connected to, participates in, or is governed by a particular league or set of leagues.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:13 p.m.