Triple
T30698652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon Z 7II |
E781548
|
entity |
| Predicate | expandedISO |
P174418
|
FINISHED |
| Object | 32–102400 |
—
|
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–102400 | Statement: [Nikon Z 7II, expandedISO, 32–102400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedISO Context triple: [Nikon Z 7II, expandedISO, 32–102400]
-
A.
expandedTerritoryOf
Indicates that one entity has increased or extended the geographic or jurisdictional area belonging to another entity.
-
B.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
-
C.
expandedTerritoryTo
Indicates that one entity has increased the geographic area under its control or influence to include the territory of another entity.
-
D.
nativeISO
Indicates that an entity inherently uses or supports a specified ISO standard or ISO-based format without requiring conversion or adaptation.
-
E.
expandedBeyondCountry
Indicates that an entity has grown or extended its operations, presence, or influence beyond the borders of its original country.
- 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_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 29, 2026, 8:34 p.m.