Triple
T9199257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 165 |
E220793
|
entity |
| Predicate | familyGeneration |
P52584
|
FINISHED |
| Object | first generation of IBM System/370 models |
—
|
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: first generation of IBM System/370 models | Statement: [IBM 165, familyGeneration, first generation of IBM System/370 models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyGeneration Context triple: [IBM 165, familyGeneration, first generation of IBM System/370 models]
-
A.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
B.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
C.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
D.
hasGenerations
chosen
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
E.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd880ab808190aa785a5f1e5d5976 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.