Triple
T30774012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon Z 8 |
E783608
|
entity |
| Predicate | maxContinuousShootingElectronic |
P170045
|
FINISHED |
| Object | 120 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: 120 fps | Statement: [Nikon Z 8, maxContinuousShootingElectronic, 120 fps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxContinuousShootingElectronic Context triple: [Nikon Z 8, maxContinuousShootingElectronic, 120 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.
flashSyncSpeedElectronic
Indicates the maximum shutter speed at which an electronic shutter can synchronize properly with a flash.
-
C.
rateOfFire
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
D.
fireControlFeature
Indicates a relationship where an entity possesses or is associated with a capability or mechanism for directing, managing, or controlling the use of fire or weapon fire.
-
E.
shotOn
Indicates that one entity fired or took a shot at another entity, typically in a sports or combat context.
- 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_69f224b1519081908b9db003fd2073e0 |
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_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:40 p.m.