Triple
T27888728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HFiles |
E705294
|
entity |
| Predicate | supportsCompressionCodec |
P64032
|
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: [HFiles, supportsCompressionCodec, GZIP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCompressionCodec Context triple: [HFiles, supportsCompressionCodec, GZIP]
-
A.
supportsCompressedFiles
Indicates that one entity is capable of handling, reading, or working with files that are stored in a compressed format.
-
B.
hasCompressor
Indicates that one entity is equipped with, contains, or uses a compressor associated with it.
-
C.
compressionType
Indicates the method or format used to compress data or content in the relationship.
-
D.
compressionStandard
Indicates that one entity uses, supports, or is defined according to a particular data compression standard specified by the other entity.
-
E.
usesCodec
chosen
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: April 27, 2026, 6:34 p.m.