Triple
T1077278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UMTS |
E23867
|
entity |
| Predicate | coreNetworkBasedOn |
P2594
|
FINISHED |
| Object | GPRS core network |
—
|
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: GPRS core network | Statement: [UMTS, coreNetworkBasedOn, GPRS core network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreNetworkBasedOn Context triple: [UMTS, coreNetworkBasedOn, GPRS core network]
-
A.
branchNetwork
Indicates that one entity operates as a branch or local outlet within the wider organizational or operational network of another entity.
-
B.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
C.
originalNetwork
chosen
Indicates that one entity is the original or source network from which another network or derived entity is based or obtained.
-
D.
operatesNetwork
Indicates that an entity manages, controls, or runs the functioning of a network.
-
E.
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).
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94288d88190aae4fb86236c0702 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.