Triple
T30644074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α7 III |
E780071
|
entity |
| Predicate | continuousShootingSpeed |
P170045
|
FINISHED |
| Object | up to 10 fps |
—
|
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: up to 10 fps | Statement: [Sony α7 III, continuousShootingSpeed, up to 10 fps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousShootingSpeed Context triple: [Sony α7 III, continuousShootingSpeed, up to 10 fps]
-
A.
maxContinuousShooting
chosen
Indicates the maximum number of photos a camera can continuously capture in rapid succession before it must pause or slow down.
-
B.
rateOfFire
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
C.
gunRate
Indicates the rate or frequency at which guns are present, owned, used, or involved in incidents within a given context.
-
D.
numberOfShotsFired
Indicates the total count of shots that were discharged in the described event or action.
-
E.
recordedShotSpeed
Indicates that a measurement has been made and stored for the speed at which a particular shot was taken.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 8:29 p.m.