Triple
T30884479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-S10 |
E786720
|
entity |
| Predicate | stabilizationStops |
P88978
|
FINISHED |
| Object | up to 6.0 stops |
—
|
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 6.0 stops | Statement: [Fujifilm X-S10, stabilizationStops, up to 6.0 stops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stabilizationStops Context triple: [Fujifilm X-S10, stabilizationStops, up to 6.0 stops]
-
A.
stabilizationOutcome
Indicates the result or state achieved after a stabilization process has been applied to something.
-
B.
stabilizationWork
Indicates actions taken to reinforce, secure, or steady something to prevent deterioration, failure, or unwanted change.
-
C.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
D.
stabilizationName
Indicates that an entity is associated with a specific name or label used for its stabilization process or stabilized form.
-
E.
stabilizationCompensation
chosen
Indicates a compensatory action or mechanism that counteracts changes or disturbances in order to maintain or restore stability in a system or process.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69204be748190a6a2a401d81c1218 |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.