Triple
T30532249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS R6 |
E777036
|
entity |
| Predicate | continuousShootingMechanical |
P170045
|
FINISHED |
| Object | up to 12 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 12 fps | Statement: [Canon EOS R6, continuousShootingMechanical, up to 12 fps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousShootingMechanical Context triple: [Canon EOS R6, continuousShootingMechanical, up to 12 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.
ammunitionFeedSystem
Indicates a mechanism or process by which ammunition is supplied or delivered to a weapon or firing system.
-
C.
hasTriggerMechanism
Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
-
D.
isGasOperated
Indicates that an entity functions or operates using gas as its primary power or energy source.
-
E.
standardIssueMachineGun
Indicates that an entity is equipped with or uses the standard-issue machine gun designated for its organization, faction, or 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 8:18 p.m.