Triple
T30532252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS R6 |
E777036
|
entity |
| Predicate | expandableISORange |
P171127
|
FINISHED |
| Object | 50–204800 |
—
|
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: 50–204800 | Statement: [Canon EOS R6, expandableISORange, 50–204800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandableISORange Context triple: [Canon EOS R6, expandableISORange, 50–204800]
-
A.
isoRangeExpandable
chosen
Indicates that the ISO range associated with an entity can be extended or adjusted beyond its default limits.
-
B.
rangeExpansion
Indicates an increase in the spatial or contextual extent over which something applies, operates, or is distributed.
-
C.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
D.
introducedRange
Indicates that an entity has brought a particular range (such as a span, interval, or set of values) into existence, use, or consideration.
-
E.
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.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 8:18 p.m.