Triple
T8651605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha YM2610 |
E205110
|
entity |
| Predicate | hasRegisterInterface |
P12981
|
FINISHED |
| Object | 8-bit parallel |
—
|
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: 8-bit parallel | Statement: [Yamaha YM2610, hasRegisterInterface, 8-bit parallel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegisterInterface Context triple: [Yamaha YM2610, hasRegisterInterface, 8-bit parallel]
-
A.
hasInterface
chosen
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
B.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
C.
hasRegisterSystem
Indicates that an entity uses or is associated with a particular register system (e.g., a system for recording, tracking, or registering items, events, or participants).
-
D.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
E.
hasInterfaceCategory
Indicates that an interface is classified as belonging to a particular category or type of interface.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc484051b48190b1d0cc63426c204d |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.