Triple
T12086487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 12 mini |
E287818
|
entity |
| Predicate | supportsSmartHDR |
P103423
|
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: [iPhone 12 mini, supportsSmartHDR, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSmartHDR Context triple: [iPhone 12 mini, supportsSmartHDR, yes]
-
A.
supportsHDRFormat
Indicates that one entity is capable of handling, displaying, or processing content encoded in a specified High Dynamic Range (HDR) format for another entity.
-
B.
supportsHDRStandard
Indicates that one entity is compatible with and can correctly handle or implement a specified HDR (High Dynamic Range) standard defined by another entity.
-
C.
supportsDolbyVisionHDRRecording
Indicates that the subject is capable of recording video content using the Dolby Vision high dynamic range (HDR) format.
-
D.
supportsColorSampling
Indicates that one entity can perform or accommodate color sampling operations on another entity or its data.
-
E.
supportsHEIF
Indicates that one entity provides compatibility with or the ability to handle HEIF (High Efficiency Image File) format for another entity.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d9178814e081908f67e3846718530e |
completed | April 10, 2026, 3:30 p.m. |
Created at: April 8, 2026, 9:48 p.m.