Triple
T30422499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPE |
E773935
|
entity |
| Predicate | vendorFamily |
P169413
|
FINISHED |
| Object | IBM Power family |
—
|
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: IBM Power family | Statement: [PPE, vendorFamily, IBM Power family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vendorFamily Context triple: [PPE, vendorFamily, IBM Power family]
-
A.
vendorType
Indicates the classification or category of a vendor based on the type of goods or services they provide.
-
B.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
C.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
D.
technologyVendor
Indicates that one entity serves as the provider or supplier of technology products or services to another entity.
-
E.
manufacturerType
Indicates the classification or category of a manufacturer based on its role, characteristics, or production 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6866596e0819096567c2f7c121936 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:06 p.m.