Triple
T16126637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AsiaInfo Telecommunication Enterprise |
E391288
|
entity |
| Predicate | domainSupported |
P60634
|
FINISHED |
| Object | .kg |
—
|
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: .kg | Statement: [AsiaInfo Telecommunication Enterprise, domainSupported, .kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainSupported Context triple: [AsiaInfo Telecommunication Enterprise, domainSupported, .kg]
-
A.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
B.
domainServed
chosen
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
C.
supportsCustomDomain
Indicates that an entity provides the capability to use or configure a custom domain name instead of a default or system-assigned domain.
-
D.
regulatoryDomainSupported
Indicates that an entity is compatible with, and can operate under, a specified regulatory domain or jurisdiction.
-
E.
testDomain
Indicates that an entity belongs to, is associated with, or is used within a specific test or testing domain.
- 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_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. |
Created at: April 10, 2026, 5 a.m.