Triple
T30924438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet in South Sudan |
E787818
|
entity |
| Predicate | mainAccessTechnology |
P73511
|
FINISHED |
| Object | mobile broadband |
—
|
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: mobile broadband | Statement: [Internet in South Sudan, mainAccessTechnology, mobile broadband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAccessTechnology Context triple: [Internet in South Sudan, mainAccessTechnology, mobile broadband]
-
A.
primaryAccessTechnologies
chosen
Indicates the main technologies or methods used to provide access or connectivity between entities.
-
B.
accessTechnology
Indicates that one entity uses, supports, or is connected via a particular communication or network access technology.
-
C.
telecommunicationsType
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
D.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
E.
telecomStandardSupported
Indicates that a system, device, or service is compatible with and can operate according to a specified telecommunications standard.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 29, 2026, 8:51 p.m.