Triple
T29181412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNIBUS |
E739753
|
entity |
| Predicate | replacedInProductLine |
P98413
|
FINISHED |
| Object | later PDP-11 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: later PDP-11 models | Statement: [UNIBUS, replacedInProductLine, later PDP-11 models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedInProductLine Context triple: [UNIBUS, replacedInProductLine, later PDP-11 models]
-
A.
replacedInProduct
Indicates that one component or element in a product has been substituted or superseded by another component or element within that product.
-
B.
replacedByInProduction
Indicates that one entity has been superseded and is no longer used in production because another specified entity has taken its place.
-
C.
replacedInNewDesignsBy
chosen
Indicates that an element or component is superseded and functionally taken over by another element or component in newer designs.
-
D.
replacedOnPlatformBy
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
-
E.
replacedByOnOrangeLine
Indicates that one entity on the Orange Line has been superseded or substituted by another entity on that same line.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 28, 2026, 11:57 a.m.