Triple

T25322021
Position Surface form Disambiguated ID Type / Status
Subject CTSS E634906 entity
Predicate hadUserInterface P1594 FINISHED
Object typewriter-like 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: typewriter-like terminals | Statement: [CTSS, hadUserInterface, typewriter-like terminals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadUserInterface
Context triple: [CTSS, hadUserInterface, typewriter-like terminals]
  • A. userInterface chosen
    Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
  • B. hasCommandLineInterface
    Indicates that an entity provides or supports interaction through a command-line interface (CLI).
  • C. supportsUserInteraction
    Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
  • D. supportsGraphicalUserInterface
    Indicates that an entity is capable of operating with or providing a graphical user interface for interaction.
  • E. hasCommunicationInterface
    Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
  • 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_69e75a9847c08190bb02990d06d5ffb7 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f4969035ac8190a35a8f6c4e4685a7 completed May 1, 2026, 12:03 p.m.
PD Predicate disambiguation batch_69f4683472ec8190a483b3b8afe71720 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 1:28 p.m.