Triple
T28608604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM VM family |
E724116
|
entity |
| Predicate | basedOnEarlierSystem |
P114341
|
FINISHED |
| Object | CP-40 |
—
|
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: CP-40 | Statement: [IBM VM family, basedOnEarlierSystem, CP-40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEarlierSystem Context triple: [IBM VM family, basedOnEarlierSystem, CP-40]
-
A.
basedOnVersion
chosen
Indicates that one entity is derived from, built upon, or created using a specific version of another entity as its basis.
-
B.
replacedEarlierSystems
Indicates that one system has taken the place of and superseded other systems that existed or were in use before it.
-
C.
previouslyUsedSystem
Indicates that an entity made use of a particular system at some time in the past, prior to the current context or state.
-
D.
previouslyBasedOn
Indicates that something was formerly derived from, adapted from, or dependent on another source, but is no longer based on it in its current state.
-
E.
replacedSystemBasedOn
Indicates that one system was substituted for another specifically on the basis of certain criteria, conditions, or evaluations.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 28, 2026, 4:28 a.m.