Triple
T29343200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godbout Electronics |
E744091
|
entity |
| Predicate | busStandardSupported |
P1587
|
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: [Godbout Electronics, busStandardSupported, S-100 bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busStandardSupported Context triple: [Godbout Electronics, busStandardSupported, S-100 bus]
-
A.
telecomStandardSupported
Indicates that a system, device, or service is compatible with and can operate according to a specified telecommunications standard.
-
B.
transmissionTypeSupported
Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
-
C.
hasSoftwareStandard
Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
-
D.
supportsBusController
Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for another entity.
-
E.
usesStandard
chosen
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
- 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_69f66928a36c8190b6a0917b0c54723e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:34 p.m.