Triple

T2834299
Position Surface form Disambiguated ID Type / Status
Subject GNU Hurd E62312 entity
Predicate supportsProcessModel P11868 FINISHED
Object servers as user-space processes 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: servers as user-space processes | Statement: [GNU Hurd, supportsProcessModel, servers as user-space processes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsProcessModel
Context triple: [GNU Hurd, supportsProcessModel, servers as user-space processes]
  • A. supportsModelType
    Indicates that an entity is compatible with, or can operate using, a specified model type.
  • B. supportsModelVariant
    Indicates that one entity is capable of operating with, being compatible with, or otherwise accommodating a specific variant of a model.
  • C. supportedParadigm chosen
    Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
  • D. supportsProgramType
    Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
  • E. supportsType
    Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
  • 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_69ab4c3c39188190955b9c49d98463d8 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdec18b808190aedae2ed11d53b15 completed March 7, 2026, 8:16 a.m.
PD Predicate disambiguation batch_69abdd0ce8b08190ba28c192988f38ce completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 10:01 p.m.