Triple
T35759706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B5000 series |
E1033537
|
entity |
| Predicate | companyLineage |
P192312
|
FINISHED |
| Object | Unisys mainframe line |
—
|
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: Unisys mainframe line | Statement: [B5000 series, companyLineage, Unisys mainframe line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyLineage Context triple: [B5000 series, companyLineage, Unisys mainframe line]
-
A.
brandLineageContinuedBy
Indicates that the continuation or successor of a brand’s lineage is carried on or maintained by another brand or entity.
-
B.
technologyLineage
Indicates a relationship where one technology is derived from, influenced by, or evolved from another in a historical or developmental sequence.
-
C.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
D.
parentCompanyFoundedByFamily
Indicates that the parent company was established or originally created by a family or family members.
-
E.
parentCompanyOfOrigin
chosen
Indicates that one company is the original parent or source company from which another company was created, derived, or spun off.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:06 p.m.