Triple
T15254830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N96 |
E364617
|
entity |
| Predicate | supportsVideoFormats |
P86386
|
FINISHED |
| Object | MPEG-4 |
—
|
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: MPEG-4 | Statement: [Nokia N96, supportsVideoFormats, MPEG-4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVideoFormats Context triple: [Nokia N96, supportsVideoFormats, MPEG-4]
-
A.
supportsVideoPlayback
chosen
Indicates that an entity is capable of playing or rendering video content.
-
B.
supportsH264
Indicates that one entity provides compatibility with, or the ability to encode/decode or process, H.264 video for another entity.
-
C.
defaultFileFormatVideo
Indicates the default file format used for saving or exporting video content.
-
D.
supportsVerticalVideo
Indicates that one entity provides compatibility with or proper handling of vertical (portrait-oriented) video content for another entity.
-
E.
supportsProResVideo
Indicates that one entity provides the capability for another entity to record, process, or handle video in the ProRes format.
- 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_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. |
Created at: April 10, 2026, 3:13 a.m.