Triple
T9728921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DECsystem-10 |
E235686
|
entity |
| Predicate | primaryInputOutput |
P90697
|
FINISHED |
| Object | teletypes and video terminals |
—
|
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: teletypes and video terminals | Statement: [DECsystem-10, primaryInputOutput, teletypes and video terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInputOutput Context triple: [DECsystem-10, primaryInputOutput, teletypes and video terminals]
-
A.
primaryInput
Indicates that an entity serves as the main or principal input to a process, system, or operation.
-
B.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
-
C.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
D.
primaryInterface
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
E.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
- F. None of above. chosen
Provenance (4 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eafa3a88190bc62924d94b89cd8 |
completed | April 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd07c5c978819084abc7267a5ced80 |
completed | April 1, 2026, 11:55 a.m. |
Created at: March 30, 2026, 8:21 p.m.