Triple
T31133946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-E3 |
E793585
|
entity |
| Predicate | storageStandard |
P8611
|
FINISHED |
| Object | UHS-I compatible |
—
|
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: UHS-I compatible | Statement: [Fujifilm X-E3, storageStandard, UHS-I compatible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageStandard Context triple: [Fujifilm X-E3, storageStandard, UHS-I compatible]
-
A.
storageProperty
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
-
B.
storageOption
chosen
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
C.
typicalStorage
Indicates the usual or standard way in which something is stored or kept.
-
D.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
E.
storageOrgan
Indicates that one entity serves as a storage organ (a specialized structure for storing substances like nutrients or water) for another entity.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:05 p.m.