Triple
T30358270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon F-mount DSLR system |
E772203
|
entity |
| Predicate | primaryStorageMedia |
P37901
|
FINISHED |
| Object | CompactFlash |
E772191
|
NE 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: CompactFlash | Statement: [Nikon F-mount DSLR system, primaryStorageMedia, CompactFlash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStorageMedia Context triple: [Nikon F-mount DSLR system, primaryStorageMedia, CompactFlash]
-
A.
primaryStorageLocation
Indicates the main or default place where an item, resource, or data is stored.
-
B.
storageDevice
Indicates a relationship where one entity functions as a device used to store data or digital information for another entity.
-
C.
secondaryStorage
Indicates that an entity serves as a secondary (non-primary) storage location or medium for another entity’s data or resources.
-
D.
storageTechnology
chosen
Indicates the type or method of data storage technology used or associated with an entity.
-
E.
primaryMediaType
Indicates the main or dominant type of media associated with an entity (for example, image, video, audio, or text).
- F. None of above.
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_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27893994548190958b3949339a6bd6 |
completed | June 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
Created at: April 29, 2026, 7:57 p.m.