Triple
T29343164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CompuPro |
E744090
|
entity |
| Predicate | offeredSystems |
P188428
|
FINISHED |
| Object | multi-board S-100 microcomputer systems |
—
|
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: multi-board S-100 microcomputer systems | Statement: [CompuPro, offeredSystems, multi-board S-100 microcomputer systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredSystems Context triple: [CompuPro, offeredSystems, multi-board S-100 microcomputer systems]
-
A.
offeredTechnology
Indicates that one entity has provided or proposed a specific technology to another entity as an option for use, adoption, or consideration.
-
B.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
C.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
-
D.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
E.
offeredOnModelType
Indicates that something is made available or provided specifically for a particular model type.
- F. None of above. chosen
Provenance (4 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_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: April 28, 2026, 1:34 p.m.