Triple

T28028706
Position Surface form Disambiguated ID Type / Status
Subject System.IO.Pipes.AnonymousPipeClientStream E708199 entity
Predicate handlePassing P93432 FINISHED
Object client handle typically passed as string to child process 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: client handle typically passed as string to child process | Statement: [System.IO.Pipes.AnonymousPipeClientStream, handlePassing, client handle typically passed as string to child process]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: handlePassing
Context triple: [System.IO.Pipes.AnonymousPipeClientStream, handlePassing, client handle typically passed as string to child process]
  • A. followsPass
    Indicates that one entity moves behind or in the path of another entity who has just passed, maintaining a trailing or subsequent position.
  • B. canBePassedTo chosen
    Indicates that one entity is capable of being transferred, handed over, or given to another entity.
  • C. hasPass
    Indicates that an entity possesses or has been granted a pass, such as a ticket, permit, or authorization to access something.
  • D. passesUnder
    Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
  • E. canPass
    Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
  • 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_69ef9b6bdd9c8190bb3a574a03774ad1 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c2198208190a3954086c22cfcbf completed May 2, 2026, 8:18 p.m.
Created at: April 27, 2026, 8:14 p.m.