Triple
T8570624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-100 bus computers |
E202915
|
entity |
| Predicate | notableVendor |
P51141
|
FINISHED |
| Object | MITS Altair (via S-100 bus origin) |
—
|
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: MITS Altair (via S-100 bus origin) | Statement: [S-100 bus computers, notableVendor, MITS Altair (via S-100 bus origin)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVendor Context triple: [S-100 bus computers, notableVendor, MITS Altair (via S-100 bus origin)]
-
A.
notableManufacturer
chosen
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
B.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
C.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
D.
notablePartner
Indicates that two entities are or have been significant partners, typically in a prominent or noteworthy personal or professional relationship.
-
E.
notableEnterprise
Indicates that an entity is a business or commercial organization recognized for its significance, prominence, or impact.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea4091f48190b5174d7a5cfd2bd8 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.