Triple
T23257993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet in Sierra Leone |
E581923
|
entity |
| Predicate | backboneType |
P151565
|
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 Sierra Leone, backboneType, fiber-optic backbone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backboneType Context triple: [Internet in Sierra Leone, backboneType, 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.
backboneAreaID
Indicates the identifier of the area or region associated with a backbone (e.g., a primary structural or network backbone).
-
C.
backType
Indicates the type or category of a backing or support associated with an entity.
-
D.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
-
E.
baseType
Indicates that one entity serves as the underlying or parent type from which another entity is derived or specialized.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:11 p.m.