Triple
T23258020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet in Sierra Leone |
E581923
|
entity |
| Predicate | cybercafeRole |
P79109
|
FINISHED |
| Object | important access point in urban areas |
—
|
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: important access point in urban areas | Statement: [Internet in Sierra Leone, cybercafeRole, important access point in urban areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cybercafeRole Context triple: [Internet in Sierra Leone, cybercafeRole, important access point in urban areas]
-
A.
ClientRole
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
-
B.
roleInCUPS
Indicates that an entity holds a specific role or function within the CUPS (Common UNIX Printing System) environment or configuration.
-
C.
siteRole
chosen
Indicates the specific function, responsibility, or position an entity holds within a particular site or location.
-
D.
roleOnLine1
Indicates that an entity holds a specific role or function associated with the first line of a multi-line structure or sequence.
-
E.
remoteTerminalRole
Indicates that an entity has a specific role or permission level when accessing or operating a system through a remote terminal.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c710c48190aff03d210642a043 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.