Triple
T31027013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP/M-68K |
E790606
|
entity |
| Predicate | inCPMLineage |
P127279
|
FINISHED |
| Object | successor to CP/M-80 |
—
|
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: successor to CP/M-80 | Statement: [CP/M-68K, inCPMLineage, successor to CP/M-80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inCPMLineage Context triple: [CP/M-68K, inCPMLineage, successor to CP/M-80]
-
A.
lineageSystem
chosen
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
B.
lineageConcept
Indicates a conceptual or abstract relationship of lineage, such as ancestry or descent, between entities.
-
C.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
D.
impliesLineage
Indicates that one entity is inferred to be ancestrally or genealogically derived from another.
-
E.
greenLineageCharacterizedBy
Indicates that a green lineage is defined or distinguished by a particular characteristic, trait, or feature.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694bf49d881908f3177f9bcfe4bf0 |
completed | May 3, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:58 p.m.