Triple
T29870986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POWER4 |
E758592
|
entity |
| Predicate | companyPlatform |
P180638
|
FINISHED |
| Object | IBM eServer pSeries |
—
|
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 eServer pSeries | Statement: [POWER4, companyPlatform, IBM eServer pSeries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyPlatform Context triple: [POWER4, companyPlatform, IBM eServer pSeries]
-
A.
corporatePlatform
Indicates a relationship where an entity serves as a corporate platform used by or provided to another entity for business-related activities or services.
-
B.
platform1Services
Indicates that one entity provides or is associated with the first platform’s services for or in relation to another entity.
-
C.
platformAppearsOn
Indicates that a particular platform is present, visible, or available within or on another specified context, medium, or environment.
-
D.
parentPlatformCompany
Indicates that one company serves as the overarching or owning platform company for another company within a corporate or business structure.
-
E.
worksOnPlatform
Indicates that an entity performs its functions, operations, or activities using or within a specified platform.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 29, 2026, 5:53 p.m.