Triple
T38263267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHA 1978–79 season |
E1017983
|
entity |
| Predicate | mergerWithLeague |
P6607
|
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: [WHA 1978–79 season, mergerWithLeague, National Hockey League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerWithLeague Context triple: [WHA 1978–79 season, mergerWithLeague, National Hockey League]
-
A.
mergedLeague
Indicates that two or more sports or competitive leagues have combined into a single unified league.
-
B.
leagueMergerAfterSeasonWith
chosen
Indicates that two or more leagues merged into a single league following the completion of a specified season.
-
C.
includesLeague
Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
-
D.
managedLeague
Indicates that one entity was responsible for organizing, directing, or overseeing the operations of a particular league.
-
E.
mergerMethod
Indicates the method or process by which two or more entities are combined or merged into a single 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.