Triple
T30485945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild |
E775720
|
entity |
| Predicate | affiliateStructure |
P169786
|
FINISHED |
| Object | NHL–AHL |
—
|
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: NHL–AHL | Statement: [Wild, affiliateStructure, NHL–AHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliateStructure Context triple: [Wild, affiliateStructure, NHL–AHL]
-
A.
affiliateOfType
Indicates that an affiliate entity belongs to, or is categorized under, a specific type or classification.
-
B.
partnerAffiliation
Indicates that two entities are formally associated as partners within an organization, project, or collaborative relationship.
-
C.
associatesStructure
Indicates a relationship where one entity is linked or connected to a particular structure, typically to denote that the structure is relevant, attached, or functionally associated with it.
-
D.
partnerStructure
Indicates a relationship where one entity is organized, configured, or structured in coordination with, or as a counterpart to, another entity in a partnership context.
-
E.
relatedCommission
Indicates that one commission is connected or associated with another commission in a relevant contextual or functional way.
- F. None of above. chosen
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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687456090819099bbbb33f6c2c048 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:13 p.m.