Triple
T33671846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartmouth Time-Sharing System |
E862637
|
entity |
| Predicate | inputOutputDevice |
P2571
|
FINISHED |
| Object | teletype 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: teletype terminals | Statement: [Dartmouth Time-Sharing System, inputOutputDevice, teletype terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputOutputDevice Context triple: [Dartmouth Time-Sharing System, inputOutputDevice, teletype terminals]
-
A.
inputDevice
chosen
Indicates that one entity functions as a device used to provide input to another entity or system.
-
B.
primaryInputOutput
Indicates that one entity serves as the main source or destination of data, signals, or materials for another entity within a process or system.
-
C.
integratedI_O
Indicates that one entity has integrated input/output functionality or operations with another entity, treating their I/O processes as a unified system.
-
D.
executionDevice
Indicates that an entity serves as the instrument, tool, or device used to carry out or execute a particular action or process.
-
E.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa3ccc348190b610bc698ea184e3 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.