Triple
T13788228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPEED |
E331321
|
entity |
| Predicate | broadcastsFormat |
P31690
|
FINISHED |
| Object | standard-definition television |
—
|
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: standard-definition television | Statement: [SPEED, broadcastsFormat, standard-definition television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastsFormat Context triple: [SPEED, broadcastsFormat, standard-definition television]
-
A.
broadcastsInFormat
chosen
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
-
B.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
C.
broadcastsIn
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
D.
radioFormat
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
E.
broadcastsTo
Indicates that one entity transmits or disseminates information, signals, or content to another entity or group of entities.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0249e4f88190a80316394940627d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.