Triple
T30698651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon Z 7II |
E781548
|
entity |
| Predicate | nativeISO |
P170486
|
FINISHED |
| Object | 64–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: 64–25600 | Statement: [Nikon Z 7II, nativeISO, 64–25600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeISO Context triple: [Nikon Z 7II, nativeISO, 64–25600]
-
A.
previousISOCode
Indicates that an entity was formerly identified by a different ISO code before its current one.
-
B.
nativeOf
Indicates that an entity originates from or was born in a particular place, region, or country.
-
C.
notNativeTo
Indicates that an entity does not originate from, or is not naturally occurring in, a specified place or environment.
-
D.
introducedAsISOCodeBy
Indicates that one entity was designated or established as an ISO code by another entity.
-
E.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 29, 2026, 8:34 p.m.