Triple
T29405477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNOME Text Editor |
E745766
|
entity |
| Predicate | supportsFileEncoding |
P33284
|
FINISHED |
| Object | UTF-8 |
—
|
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: UTF-8 | Statement: [GNOME Text Editor, supportsFileEncoding, UTF-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFileEncoding Context triple: [GNOME Text Editor, supportsFileEncoding, UTF-8]
-
A.
supportsCompressedFiles
Indicates that one entity is capable of handling, reading, or working with files that are stored in a compressed format.
-
B.
supportsUnicode
chosen
Indicates that an entity is capable of correctly handling, storing, or displaying Unicode-encoded text.
-
C.
hasExtendedCharacterSet
Indicates that an entity supports or uses a character set that goes beyond a basic or standard set of characters.
-
D.
supportsTextFormat
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
E.
supportsMultipleFiles
Indicates that the subject is capable of handling, processing, or operating on more than one file at the same time.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a036b0755888190a68a673664f0ea46 |
completed | May 12, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_6a036228676c8190aac9c90f7d8cedf7 |
completed | May 12, 2026, 5:23 p.m. |
Created at: April 28, 2026, 2:54 p.m.