Triple
T38023818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6680 |
E948712
|
entity |
| Predicate | supportsVideoStreaming |
P74467
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nokia 6680, supportsVideoStreaming, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVideoStreaming Context triple: [Nokia 6680, supportsVideoStreaming, yes]
-
A.
supportsStreamingIn
Indicates that one entity provides or enables streaming functionality within a specified context, environment, or medium.
-
B.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
-
C.
hasIntegratedVideo
Indicates that an entity includes built-in video capabilities as an integral part of itself, rather than relying on an external video component.
-
D.
supportsVideoCalling
Indicates that one entity provides or enables video calling functionality for another entity.
-
E.
supportsStreamingWithoutDownload
chosen
Indicates that one entity enables another to access or play content via streaming in real time without requiring the content to be downloaded first.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.