Triple
T31008904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-E1 |
E790151
|
entity |
| Predicate | hasManualControls |
P201377
|
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: [Fujifilm X-E1, hasManualControls, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManualControls Context triple: [Fujifilm X-E1, hasManualControls, true]
-
A.
hasManual
Indicates that an entity is associated with a manual that provides instructions or documentation for it.
-
B.
hasMotionControls
Indicates that an entity supports or involves control through physical movement or gestures rather than (or in addition to) traditional input methods.
-
C.
isManualPlayable
Indicates that something can be performed or operated manually by a person, rather than automatically or by a system.
-
D.
isRemoteControlled
Indicates that an entity is operated or controlled from a distance via a remote device or system.
-
E.
hasPhysicalControl
Indicates that one entity currently exercises direct, tangible control or possession over another entity or object.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
| PDg | Predicate description generation | batch_69ffef8003c081909ec2413b4ea08d43 |
completed | May 10, 2026, 2:37 a.m. |
Created at: April 29, 2026, 8:57 p.m.