Triple
T30338937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POWER10 |
E771694
|
entity |
| Predicate | firstSystemsShippedBy |
P31505
|
FINISHED |
| Object | IBM Power Systems |
E204899
|
NE 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: IBM Power Systems | Statement: [POWER10, firstSystemsShippedBy, IBM Power Systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSystemsShippedBy Context triple: [POWER10, firstSystemsShippedBy, IBM Power Systems]
-
A.
firstShippedOn
Indicates the date on which something was initially shipped or dispatched for the first time.
-
B.
firstDeployedIn
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
-
C.
wasFirstCommercializedBy
Indicates that the subject was initially brought to market or made commercially available by the object.
-
D.
firstShippedWith
chosen
Indicates that one entity was the initial product, version, or item to be delivered, released, or included together with another entity.
-
E.
wasFirstProducedBy
Indicates that something (such as a product, work, or item) was initially created, manufactured, or brought into existence by a particular agent, organization, or producer.
- F. None of above.
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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01ccd995e48190b6675e463bd0a567 |
completed | May 11, 2026, 12:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27be580dc08190a815c1029541ebd6 |
completed | June 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a01cc33177c8190bc0703276618b3ec |
completed | May 11, 2026, 12:31 p.m. |
Created at: April 29, 2026, 7:55 p.m.