Triple
T9550244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α6000 series |
E230402
|
entity |
| Predicate | supportsContinuousShooting |
P87755
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sony α6000 series, supportsContinuousShooting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContinuousShooting Context triple: [Sony α6000 series, supportsContinuousShooting, true]
-
A.
supportsBurstMode
chosen
Indicates that an entity is capable of operating in a burst mode, handling short periods of intensified or rapid activity beyond its normal continuous capacity.
-
B.
shotOn
Indicates that one entity fired or took a shot at another entity, typically in a sports or combat context.
-
C.
supportsCameraControl
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
-
D.
shotFrom
Indicates that something is propelled or discharged starting at a particular source or origin.
-
E.
shoots
Indicates that one entity propels a projectile or discharge toward another entity, typically with the intent to hit or affect it.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9906bc90819086f105c453e63c83 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:02 p.m.