Triple
T30007562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LBA |
E762364
|
entity |
| Predicate | definedAtInterfaceLevel |
P177306
|
FINISHED |
| Object | host-to-disk interface |
—
|
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: host-to-disk interface | Statement: [LBA, definedAtInterfaceLevel, host-to-disk interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedAtInterfaceLevel Context triple: [LBA, definedAtInterfaceLevel, host-to-disk interface]
-
A.
usedInInterface
Indicates that something is employed or incorporated as a component or element within a user interface.
-
B.
definesInterfaceProtocol
Indicates that one entity specifies or establishes the communication or interaction protocol that another entity must follow as its interface.
-
C.
interfaceLevel
chosen
Indicates the degree or layer at which two systems, components, or entities interact or exchange information through an interface.
-
D.
coversInterface
Indicates that one entity provides or implements the functionality defined by a specified interface.
-
E.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 29, 2026, 6:43 p.m.