Triple
T33244351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM PS/2 |
E851052
|
entity |
| Predicate | expansionBusType |
P175660
|
FINISHED |
| Object | proprietary |
—
|
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: proprietary | Statement: [IBM PS/2, expansionBusType, proprietary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionBusType Context triple: [IBM PS/2, expansionBusType, proprietary]
-
A.
expansionBus
Indicates a hardware connection through which a device can be attached to or communicate over an expansion bus.
-
B.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
C.
expansionSlots
Indicates that an entity provides one or more hardware expansion slots available for adding additional components or capabilities.
-
D.
hasBusType
chosen
Indicates that one entity (typically a bus or bus service) is associated with or classified by a specific type or category of bus.
-
E.
expansionOptions
Indicates the available ways or configurations in which something can be extended, enlarged, or further developed.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:31 a.m.