Triple
T16126667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet in Kyrgyzstan |
E391289
|
entity |
| Predicate | hasBackboneType |
P841
|
FINISHED |
| Object | fiber-optic backbone |
—
|
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: fiber-optic backbone | Statement: [Internet in Kyrgyzstan, hasBackboneType, fiber-optic backbone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackboneType Context triple: [Internet in Kyrgyzstan, hasBackboneType, fiber-optic backbone]
-
A.
isCombinationBackboneWith
Indicates a structural relationship where one entity serves as a backbone or core framework that is combined with another entity to form a composite or integrated whole.
-
B.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
-
C.
hasSkeleton
Indicates that an entity possesses a skeleton as part of its bodily structure.
-
D.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
E.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
- 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.