Triple
T29343105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cromemco |
E744089
|
entity |
| Predicate | usedHardwareStandard |
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: [Cromemco, usedHardwareStandard, S-100 bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHardwareStandard Context triple: [Cromemco, usedHardwareStandard, S-100 bus]
-
A.
usesStandard
chosen
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
B.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
C.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
D.
usedAsStandard
Indicates that one entity serves as the reference or benchmark against which another entity is measured, compared, or evaluated.
-
E.
standardsUsedIn
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or 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_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.