Triple
T31008806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α7S II |
E790149
|
entity |
| Predicate | isoRangeExpanded |
P29849
|
FINISHED |
| Object | ISO 50–409600 |
—
|
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: ISO 50–409600 | Statement: [Sony α7S II, isoRangeExpanded, ISO 50–409600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isoRangeExpanded Context triple: [Sony α7S II, isoRangeExpanded, ISO 50–409600]
-
A.
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.
-
B.
rangeExpansion
Indicates an increase in the spatial or contextual extent over which something applies, operates, or is distributed.
-
C.
isoScope
Indicates that one entity defines or constrains the scope or boundary within which another entity is considered equivalent or comparable.
-
D.
introducedRange
chosen
Indicates that an entity has brought a particular range (such as a span, interval, or set of values) into existence, use, or consideration.
-
E.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
- F. None of above.
Provenance (3 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.