Triple
T30698663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon Z 7II |
E781548
|
entity |
| Predicate | maxContinuousShooting |
P170045
|
FINISHED |
| Object | 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: 10 fps | Statement: [Nikon Z 7II, maxContinuousShooting, 10 fps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxContinuousShooting Context triple: [Nikon Z 7II, maxContinuousShooting, 10 fps]
-
A.
rateOfFire
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
B.
numberOfShotsFired
Indicates the total count of shots that were discharged in the described event or action.
-
C.
gunRate
Indicates the rate or frequency at which guns are present, owned, used, or involved in incidents within a given context.
-
D.
fireControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the detection, targeting, and firing of weapons or other actuators to control the application of force or energy.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68bdceb8c8190b78e499ea2357e0f |
completed | May 2, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:34 p.m.