Triple
T35930358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL Network |
E1039142
|
entity |
| Predicate | hasProgrammingFeature |
P182
|
FINISHED |
| Object | studio analysis |
—
|
LITERAL 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: studio analysis | Statement: [NHL Network, hasProgrammingFeature, studio analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammingFeature Context triple: [NHL Network, hasProgrammingFeature, studio analysis]
-
A.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
B.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
hasProgrammingModel
Indicates that one entity defines, specifies, or is associated with the programming model used or supported by another entity.
-
D.
programmingFeature
Indicates a relationship where one entity is a specific programming-related capability, construct, or functionality provided or supported by another entity (such as a language, tool, or system).
-
E.
hasSideFeature
Indicates that an entity possesses a specific secondary or auxiliary feature on its side or lateral aspect.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.