Triple
T30774007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon Z 8 |
E783608
|
entity |
| Predicate | nativeISOmin |
P170799
|
FINISHED |
| Object | 64 |
—
|
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: 64 | Statement: [Nikon Z 8, nativeISOmin, 64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeISOmin Context triple: [Nikon Z 8, nativeISOmin, 64]
-
A.
nativeISO
Indicates that an entity inherently uses or supports a specified ISO standard or ISO-based format without requiring conversion or adaptation.
-
B.
isoRangeNative
Indicates that two values fall within the same native ISO-defined range or interval, according to the system’s inherent ISO-based scale or categorization.
-
C.
minimumMass
Indicates the smallest mass value that an entity or system is required, allowed, or observed to have within a given context.
-
D.
minimumDenomination
Indicates that one entity specifies the smallest allowable unit or value (minimum denomination) in which another entity can be expressed, transacted, or divided.
-
E.
isSmallestOf
Indicates that an entity has the minimum size or value within a specified set or group of entities.
- 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_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:40 p.m.