Triple
T15254817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N96 |
E364617
|
entity |
| Predicate | hasDVB-H |
P117788
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nokia N96, hasDVB-H, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDVB-H Context triple: [Nokia N96, hasDVB-H, true]
-
A.
hasDigitalSubchannels
Indicates that a broadcasting entity provides one or more additional digital subchannels alongside its primary digital channel.
-
B.
hasDigitalSignal
Indicates that an entity possesses, carries, or is associated with a digital (discrete-valued) signal.
-
C.
hdChannel
Indicates that a media service or content stream is provided in high-definition (HD) format.
-
D.
enables4KUHDOverTheAir
Indicates that one entity provides the capability for another to support or deliver 4K Ultra High Definition content via over-the-air transmission.
-
E.
backwardsCompatibleWithATSC1.0Receivers
Indicates that something can operate correctly with and be received or decoded by ATSC 1.0-compatible receivers without requiring modifications to those receivers.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f8cb308190933c4478aa096e24 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.