Triple
T29181773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI OMAP3430 |
E739762
|
entity |
| Predicate | hasBusInterface |
P34297
|
FINISHED |
| Object | USB |
—
|
NE NERFINISHED |
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 | Statement: [TI OMAP3430, hasBusInterface, USB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusInterface Context triple: [TI OMAP3430, hasBusInterface, USB]
-
A.
hasBusArchitecture
Indicates that one entity uses, implements, or is characterized by a particular bus architecture in its design or operation.
-
B.
hasCommunicationInterface
chosen
Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
-
C.
hasBusType
Indicates that one entity (typically a bus or bus service) is associated with or classified by a specific type or category of bus.
-
D.
hasBusArbitration
Indicates that one entity manages or participates in the control and coordination of access to a shared communication bus among multiple entities.
-
E.
supportsBusController
Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 11:57 a.m.