Triple
T30949414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α7R V |
E788493
|
entity |
| Predicate | phaseDetectionPoints |
P43058
|
FINISHED |
| Object | 693 phase-detection points |
—
|
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: 693 phase-detection points | Statement: [Sony α7R V, phaseDetectionPoints, 693 phase-detection points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseDetectionPoints Context triple: [Sony α7R V, phaseDetectionPoints, 693 phase-detection points]
-
A.
phaseIndicatedBy
Indicates that a particular phase or stage is determined, signaled, or specified by a given indicator or reference.
-
B.
timingOfPoints
Indicates the temporal relationship or sequence in which the points or events occur.
-
C.
phaseCount
chosen
Indicates the number of distinct phases or stages associated with a given process, event, or entity.
-
D.
phaseDifferenceDependsOn
Indicates that the phase difference between two signals or waves is determined by, or varies as a function of, another specified quantity or condition.
-
E.
phaseUsed
Indicates that a particular phase, stage, or step is utilized or applied in carrying out an action, process, or relationship.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:53 p.m.