Triple
T29924448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Media in Eritrea |
E760039
|
entity |
| Predicate | internetAccessLevel |
P73512
|
FINISHED |
| Object | very low |
—
|
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: very low | Statement: [Media in Eritrea, internetAccessLevel, very low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internetAccessLevel Context triple: [Media in Eritrea, internetAccessLevel, very low]
-
A.
networkAccessTo
Indicates that one entity has the ability or permission to reach, communicate with, or use another entity over a network.
-
B.
internetPenetration
chosen
Indicates the extent to which access to and use of the internet is available among a given population or within a specific area.
-
C.
networkLevel
Indicates the hierarchical position or tier an entity occupies within a network structure.
-
D.
networkRequirement
Indicates that one entity requires access to or use of another entity’s network resources or connectivity to function or be fulfilled.
-
E.
humanAccessLevel
Indicates the level or degree of access or permissions granted to a human within a system or context.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 6:15 p.m.