Triple
T33433805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DecompressionStream |
E856196
|
entity |
| Predicate | hasConstructorSignature |
—
|
GENERATED |
| Object | new DecompressionStream(format) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructorSignature Context triple: [DecompressionStream, hasConstructorSignature, new DecompressionStream(format)]
-
A.
hasConstructor
Indicates that an entity defines or is associated with a specific constructor used to create or initialize instances of it.
-
B.
hasConstructorType
chosen
Indicates that an entity is associated with, or defined by, a specific type of constructor (e.g., a particular construction method, pattern, or signature).
-
C.
hasMethodSignature
Indicates that a method or function is associated with a specific formal signature, including its name, parameters, and return type.
-
D.
hasTypeConstructor
Indicates that an entity is associated with or defined by a specific type constructor used to build or parameterize its type.
-
E.
usesConstructor
Indicates that one entity creates or initializes another entity by invoking its constructor.
- F. None of above.
Provenance (1 batch)
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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.