Triple
T34542027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Openmoko Neo 1973 |
E886828
|
entity |
| Predicate | hasFlashStorage |
P85952
|
FINISHED |
| Object | 64 MB |
—
|
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: 64 MB | Statement: [Openmoko Neo 1973, hasFlashStorage, 64 MB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlashStorage Context triple: [Openmoko Neo 1973, hasFlashStorage, 64 MB]
-
A.
hasFlash
Indicates that an entity is equipped with or supports a flash feature, typically for illumination in imaging or photography.
-
B.
hasStorage
chosen
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
C.
hasStorageFunction
Indicates that an entity serves to store, retain, or hold another entity or resource for later use.
-
D.
hasMemoryIn
Indicates that an entity possesses or stores memory, information, or experiences within a specified context, location, or medium.
-
E.
hasUserMemory
Indicates that an entity maintains or is associated with stored information about a specific user.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.