Triple
T16126675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet in Kyrgyzstan |
E391289
|
entity |
| Predicate | accessTechnology |
P121569
|
FINISHED |
| Object | ADSL |
—
|
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: ADSL | Statement: [Internet in Kyrgyzstan, accessTechnology, ADSL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessTechnology Context triple: [Internet in Kyrgyzstan, accessTechnology, ADSL]
-
A.
accessModelIntroduced
Indicates that a particular method, mechanism, or pathway for accessing something has been newly introduced or made available.
-
B.
enablesTechnology
Indicates that one entity makes it possible for another entity, system, or process to function through the use or provision of a particular technology.
-
C.
accessibilityFeatures
Indicates the specific tools, settings, or design elements provided to make something usable or understandable for people with disabilities or diverse access needs.
-
D.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
E.
technologyInteractedWith
Indicates that an entity has used, engaged with, or otherwise interacted with a particular technology.
- F. None of above. chosen
Provenance (4 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20204fb408190b58d49d0d64bb740 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.