Triple
T34955658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | qemacs |
E1008116
|
entity |
| Predicate | supportsMultipleEncodings |
P82555
|
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: [qemacs, supportsMultipleEncodings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleEncodings Context triple: [qemacs, supportsMultipleEncodings, true]
-
A.
supportsUnicode
Indicates that an entity is capable of correctly handling, storing, or displaying Unicode-encoded text.
-
B.
encodingIndependence
chosen
Indicates that a relationship or property holds regardless of the specific encoding or representation used for the involved entities.
-
C.
supportsMultipleFiles
Indicates that the subject is capable of handling, processing, or operating on more than one file at the same time.
-
D.
hasExtendedCharacterSet
Indicates that an entity supports or uses a character set that goes beyond a basic or standard set of characters.
-
E.
usesEncodingRules
Indicates that one entity applies or conforms to a specified set of encoding rules when representing or transforming information.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.