Triple
T33433769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CompressionStream |
E856195
|
entity |
| Predicate | formatAllowedValue |
P50153
|
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: [CompressionStream, formatAllowedValue, "gzip"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatAllowedValue Context triple: [CompressionStream, formatAllowedValue, "gzip"]
-
A.
formatRequirement
Indicates that one entity specifies the required structure, style, or arrangement that another entity must follow or conform to.
-
B.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
C.
formatStrategy
Indicates the method or approach used to structure, arrange, or present information or content.
-
D.
multipleValuesAllowed
Indicates that the relationship or attribute can be associated with more than one value simultaneously, rather than being restricted to a single value.
-
E.
enforcedValue
chosen
Indicates that a specific value is imposed or mandated for an entity, leaving no freedom to choose an alternative.
- 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_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:36 a.m.