Triple
T33057175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC-256 |
E845873
|
entity |
| Predicate | statusInESTREAM |
P80625
|
FINISHED |
| Object | recommended cipher |
—
|
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: recommended cipher | Statement: [HC-256, statusInESTREAM, recommended cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInESTREAM Context triple: [HC-256, statusInESTREAM, recommended cipher]
-
A.
streamingStatus
Indicates the current state or condition of an ongoing or potential media stream, such as whether it is active, paused, stopped, or unavailable.
-
B.
hasStreamingEligibility
Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
-
C.
hasStreamingAvailability
chosen
Indicates that a media item is available to be streamed through a particular streaming service or platform.
-
D.
statusInTVSeries
Indicates the role or standing an entity holds within a particular TV series, such as main, recurring, or guest status.
-
E.
statusTransmission
Indicates that a status or state is being communicated or passed from one entity to another.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1:25 a.m.