Triple
T29372141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPM |
E744881
|
entity |
| Predicate | registerInterface |
P11686
|
FINISHED |
| Object | 8-bit parallel bus |
—
|
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 bus | Statement: [OPM, registerInterface, 8-bit parallel bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerInterface Context triple: [OPM, registerInterface, 8-bit parallel bus]
-
A.
relatedInterface
Indicates that one interface is associated or connected to another interface in a relevant or dependent way.
-
B.
usesInterface
chosen
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
C.
mountingInterface
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
D.
definesInterfaceProtocol
Indicates that one entity specifies or establishes the communication or interaction protocol that another entity must follow as its interface.
-
E.
publicInterface
Indicates that an entity exposes a publicly accessible interface through which other entities can interact with it.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 2:28 p.m.