Triple
T21092597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abkhaz Cyrillic alphabet |
E519671
|
entity |
| Predicate | supportsDigitalUse |
P15794
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Abkhaz Cyrillic alphabet, supportsDigitalUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDigitalUse Context triple: [Abkhaz Cyrillic alphabet, supportsDigitalUse, yes]
-
A.
supportsUse
chosen
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
B.
usedInDigitalMedia
Indicates that something is employed, featured, or incorporated within digital media content or platforms.
-
C.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
D.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
E.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e70950a31c8190bde2d7b414c362c7 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:51 p.m.