Triple
T16381834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ondangwa |
E397823
|
entity |
| Predicate | hasCommunicationServices |
P43020
|
FINISHED |
| Object | mobile networks |
—
|
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 networks | Statement: [Ondangwa, hasCommunicationServices, mobile networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunicationServices Context triple: [Ondangwa, hasCommunicationServices, mobile networks]
-
A.
usesTelecommunications
Indicates that one entity communicates with or transmits information to another by means of telecommunications technologies or networks.
-
B.
communicationCapability
chosen
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
C.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
D.
hasTelecommunicationsRole
Indicates that an entity holds or performs a specific function, position, or responsibility within the field of telecommunications.
-
E.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319dd0e0c8190812bde6a2f7d9644 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.