Triple
T1926919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian language |
E40852
|
entity |
| Predicate | hasDigitalInputLayout |
P5738
|
FINISHED |
| Object | Georgian keyboard layout |
—
|
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: Georgian keyboard layout | Statement: [Georgian language, hasDigitalInputLayout, Georgian keyboard layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalInputLayout Context triple: [Georgian language, hasDigitalInputLayout, Georgian keyboard layout]
-
A.
hasKeypadLayout
chosen
Indicates that one entity possesses or uses a specific arrangement or configuration of keys or buttons provided by another entity.
-
B.
hasDigitalEncoding
Indicates that one entity is represented, stored, or expressed using a specific digital code or encoding scheme provided by another entity.
-
C.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
D.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
-
E.
isAnalogOrDigital
Indicates whether something operates using analog signals/representation or digital signals/representation.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb261ef8481909be2390ac5a02622 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.