Triple
T29343160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CompuPro |
E744090
|
entity |
| Predicate | usedBusArchitecture |
P79786
|
FINISHED |
| Object | S-100 bus |
—
|
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: S-100 bus | Statement: [CompuPro, usedBusArchitecture, S-100 bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBusArchitecture Context triple: [CompuPro, usedBusArchitecture, S-100 bus]
-
A.
hasBusArchitecture
chosen
Indicates that one entity uses, implements, or is characterized by a particular bus architecture in its design or operation.
-
B.
usesBus
Indicates that an entity regularly travels or transports itself by means of a bus.
-
C.
usesServiceBasedArchitecture
Indicates that one entity designs or operates its system using a service-based architecture, where functionality is organized into distinct, interacting services.
-
D.
spacecraftBus
Indicates that one entity serves as the primary structural and support platform (bus) for a spacecraft, integrating and housing its subsystems.
-
E.
exampleArchitecture
Indicates that one entity serves as a representative or illustrative instance of the architectural style, structure, or design of 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 1:34 p.m.