Triple
T30774009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon Z 8 |
E783608
|
entity |
| Predicate | expandedISOmin |
P175276
|
FINISHED |
| Object | 32 |
—
|
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: 32 | Statement: [Nikon Z 8, expandedISOmin, 32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedISOmin Context triple: [Nikon Z 8, expandedISOmin, 32]
-
A.
expandedISO
Indicates that one entity is an expanded or more detailed version of another entity according to ISO standards or formats.
-
B.
nativeISOmin
Indicates that the subject entity has a minimum native ISO sensitivity value equal to the specified object value.
-
C.
nativeISOmax
Indicates the maximum native ISO sensitivity a camera sensor can achieve without using extended or boosted ISO modes.
-
D.
nativeISO
Indicates that an entity inherently uses or supports a specified ISO standard or ISO-based format without requiring conversion or adaptation.
-
E.
isoRangeExpandable
Indicates that the ISO range associated with an entity can be extended or adjusted beyond its default limits.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 29, 2026, 8:40 p.m.