Triple
T25274604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTN Group |
E633660
|
entity |
| Predicate | coreNetworkTechnology |
P73511
|
FINISHED |
| Object | 3G |
—
|
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: 3G | Statement: [MTN Group, coreNetworkTechnology, 3G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreNetworkTechnology Context triple: [MTN Group, coreNetworkTechnology, 3G]
-
A.
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).
-
B.
supportedNetwork
Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
-
C.
primaryAccessTechnologies
chosen
Indicates the main technologies or methods used to provide access or connectivity between entities.
-
D.
networkCharacteristic
Indicates a relationship where a specific property or feature is attributed to a network or networking context.
-
E.
networkTypeFounded
Indicates that a particular type of network was established or created at a specific time or by a specific agent.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba5024c8190acce739b3b97bdb8 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:17 p.m.