Triple
T28568715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strix Television |
E722752
|
entity |
| Predicate | formatExportedTo |
P5775
|
FINISHED |
| Object | multiple international markets |
—
|
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: multiple international markets | Statement: [Strix Television, formatExportedTo, multiple international markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatExportedTo Context triple: [Strix Television, formatExportedTo, multiple international markets]
-
A.
canExportToFormat
Indicates that something has the capability to be exported or converted into a specified file or data format.
-
B.
exportedTo
chosen
Indicates that goods, services, or resources are sent out from one entity or region to another for trade or sale.
-
C.
exportedAs
Indicates that something is made available or delivered to an external destination under a specified name, format, or representation.
-
D.
handlesExport
Indicates that an entity is responsible for managing or processing the export of goods, data, or resources from one context or location to another.
-
E.
isExported
Indicates that an entity is sent out or transferred from its origin to an external destination or system.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 4:08 a.m.