Triple
T30774008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon Z 8 |
E783608
|
entity |
| Predicate | nativeISOmax |
P171095
|
FINISHED |
| Object | 25600 |
—
|
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: 25600 | Statement: [Nikon Z 8, nativeISOmax, 25600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeISOmax Context triple: [Nikon Z 8, nativeISOmax, 25600]
-
A.
nativeISO
Indicates that an entity inherently uses or supports a specified ISO standard or ISO-based format without requiring conversion or adaptation.
-
B.
nativeISOmin
Indicates that the subject entity has a minimum native ISO sensitivity value equal to the specified object value.
-
C.
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.
-
D.
previousISOCode
Indicates that an entity was formerly identified by a different ISO code before its current one.
-
E.
isInternationalStandard
Indicates that something has been formally recognized or adopted as a standard at the international level.
- 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_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:40 p.m.