Triple

T2690618
Position Surface form Disambiguated ID Type / Status
Subject Matt Johnston E58391 entity
Predicate programmingDomain P37802 FINISHED
Object secure shell software 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: secure shell software | Statement: [Matt Johnston, programmingDomain, secure shell software]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: programmingDomain
Context triple: [Matt Johnston, programmingDomain, secure shell software]
  • A. programmingLanguage
    Indicates that one entity is a programming language used to create, control, or interact with the other entity.
  • B. softwareDomain chosen
    Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
  • C. programming
    Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
  • D. programmingFocus
    Indicates a relationship where an entity’s primary attention, effort, or specialization is directed toward a particular area or aspect of programming.
  • E. programmingIncludes
    Indicates that one programming-related entity contains, incorporates, or makes use of another as a part, feature, or component.
  • 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_69ab4ac269e481909cb317d79e68b75b completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abda0ba2208190ad87763ecbef8c3c completed March 7, 2026, 7:55 a.m.
PD Predicate disambiguation batch_69abd81c9b4c81908e5e0da6ac5f828b completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:54 p.m.