Triple
T34955661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | qemacs |
E1008116
|
entity |
| Predicate | supportsLatin1 |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLatin1 Context triple: [qemacs, supportsLatin1, true]
-
A.
supportsUnicode
Indicates that an entity is capable of correctly handling, storing, or displaying Unicode-encoded text.
-
B.
hasLatinText
Indicates that an entity possesses or is associated with text written in Latin.
-
C.
usesLatinAlphabetSince
Indicates that an entity has employed the Latin alphabet as its writing system starting from a specific point in time and continuing thereafter.
-
D.
hasLatinAlphabetStandard
Indicates that there exists an established standard or convention for representing something using the Latin alphabet.
-
E.
hasUnicode
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4 p.m.