Triple
T33433808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DecompressionStream |
E856196
|
entity |
| Predicate | formatParameterAllowedValue |
P130119
|
FINISHED |
| Object | "gzip" |
—
|
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: "gzip" | Statement: [DecompressionStream, formatParameterAllowedValue, "gzip"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatParameterAllowedValue Context triple: [DecompressionStream, formatParameterAllowedValue, "gzip"]
-
A.
multipleValuesAllowed
Indicates that the relationship or attribute can be associated with more than one value simultaneously, rather than being restricted to a single value.
-
B.
genericParameter
Indicates that one entity functions as a type or template parameter that is supplied to or constrained by another entity.
-
C.
canTakeValue
Indicates that a given entity is capable of assuming, being assigned, or exhibiting a particular value.
-
D.
possibleValue
chosen
Indicates that a given value is one of the allowed or valid options for a particular attribute, parameter, or variable.
-
E.
hasParameterization
Indicates that one entity serves as the specific parameterization or parameter-setting scheme used to define or configure 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:36 a.m.