Triple
T31992510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7-Zip |
E816907
|
entity |
| Predicate | supportsUnicodeFilenames |
P33284
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [7-Zip, supportsUnicodeFilenames, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsUnicodeFilenames Context triple: [7-Zip, supportsUnicodeFilenames, true]
-
A.
supportsLongFilenames
Indicates that an entity is capable of handling, storing, or processing filenames that exceed a standard or traditional length limit.
-
B.
supportsUnicode
chosen
Indicates that an entity is capable of correctly handling, storing, or displaying Unicode-encoded text.
-
C.
supportsCaseSensitiveFilenames
Indicates that the subject is capable of handling or distinguishing filenames based on letter casing, treating differently cased names as distinct.
-
D.
hasUnicode
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
-
E.
supportsRegionalFileSystems
Indicates that an entity provides compatibility with or functionality for file systems specific to particular regions or locales.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:13 a.m.