Triple
T28028676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IO.Pipes.AnonymousPipeClientStream |
E708199
|
entity |
| Predicate | pipeType |
P163641
|
FINISHED |
| Object | anonymous pipe |
—
|
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: anonymous pipe | Statement: [System.IO.Pipes.AnonymousPipeClientStream, pipeType, anonymous pipe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pipeType Context triple: [System.IO.Pipes.AnonymousPipeClientStream, pipeType, anonymous pipe]
-
A.
pipeDiameter
Indicates that one entity specifies or measures the diameter of a pipe associated with another entity.
-
B.
pipelineTo
Indicates that data, output, or results from one process, component, or stage are directed and fed as input into another in a sequential flow.
-
C.
pipeline
Indicates a sequential process or workflow where the output of one stage is passed as input to the next to achieve a final result.
-
D.
inletType
Indicates the specific kind or category of inlet through which something (such as a fluid, signal, or material) enters a system or component.
-
E.
penstockType
Indicates the specific kind or classification of a penstock used in a water conveyance or hydroelectric system.
- F. None of above. chosen
Provenance (4 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_69f63c709b7c81909afc14cb51f43bb8 |
completed | May 2, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:14 p.m.