Triple
T30358369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-mount |
E772205
|
entity |
| Predicate | hasOfficialSpeedBoosterSupport |
P177574
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fujifilm X-mount, hasOfficialSpeedBoosterSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialSpeedBoosterSupport Context triple: [Fujifilm X-mount, hasOfficialSpeedBoosterSupport, yes]
-
A.
supportsTurboBoost
Indicates that one entity provides or is compatible with Turbo Boost functionality for another entity or process.
-
B.
hasTopSpeedSection
Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
-
C.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
D.
hasHighSpeedQuads
Indicates that the subject possesses quad-based components or mechanisms capable of operating at high speed.
-
E.
hasBoostMechanic
Indicates that one entity (typically a game or system) includes a mechanic that temporarily increases the power, speed, or effectiveness of another entity.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 29, 2026, 7:57 p.m.