Triple
T13777467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roland TR-08 |
E331045
|
entity |
| Predicate | hasPowerOption |
P74459
|
FINISHED |
| Object | USB bus power |
—
|
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: USB bus power | Statement: [Roland TR-08, hasPowerOption, USB bus power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerOption Context triple: [Roland TR-08, hasPowerOption, USB bus power]
-
A.
powerOption
chosen
Indicates that one entity provides or specifies a particular power-related configuration or choice available to another entity.
-
B.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
C.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
D.
hasPowerRegulator
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
-
E.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0239cbfc81909064ac2457fdfff5 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.