Triple
T34542050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Openmoko Neo 1973 |
E886828
|
entity |
| Predicate | hasOpenSchematics |
P166726
|
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: [Openmoko Neo 1973, hasOpenSchematics, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpenSchematics Context triple: [Openmoko Neo 1973, hasOpenSchematics, yes]
-
A.
openSourceHardware
chosen
Indicates that the hardware design is publicly available under an open license, allowing others to study, modify, and redistribute it.
-
B.
hasPuzzleDesign
Indicates that one entity is responsible for creating, planning, or defining the structure and content of a puzzle associated with another entity.
-
C.
hasPartInHisDesign
Indicates that one entity is included as a component or element within the design or plan created by another entity.
-
D.
isOpenDesign
Indicates that something is created or developed using an open, publicly accessible design process that allows use, modification, and sharing by others.
-
E.
canBeOpenedBy
Indicates that one entity has the ability or permission to open 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 2:02 a.m.