Triple

T25372308
Position Surface form Disambiguated ID Type / Status
Subject Linux /proc file system E632960 entity
Predicate kernelParametersInterface P82505 FINISHED
Object /proc/sys 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: /proc/sys | Statement: [Linux /proc file system, kernelParametersInterface, /proc/sys]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: kernelParametersInterface
Context triple: [Linux /proc file system, kernelParametersInterface, /proc/sys]
  • A. kernelProperty
    Indicates that a property or attribute is fundamental, central, or core to the structure or behavior of a given system or object.
  • B. keyParameter
    Indicates that one entity functions as a primary or critical parameter that significantly influences or determines the behavior, outcome, or configuration of another entity.
  • C. kernelDefines
    Indicates that a kernel (core component or subsystem) specifies or establishes the structure, behavior, or rules governing another element.
  • D. kernelInterfaceIntroduced chosen
    Indicates that a new interface has been added or exposed within the kernel.
  • E. genericParameter
    Indicates that one entity functions as a type or template parameter that is supplied to or constrained 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_69e75a90c0dc819092f928b6ea0ecc72 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f55e519978819087a1676564a74630 completed May 2, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69f45d0dbc8c8190beecce679fce90a4 completed May 1, 2026, 7:58 a.m.
Created at: April 21, 2026, 1:38 p.m.