Triple
T23302409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP2 |
E590337
|
entity |
| Predicate | usesCoreNetworkModel |
P151788
|
FINISHED |
| Object | IP-based 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: IP-based core network | Statement: [3GPP2, usesCoreNetworkModel, IP-based core network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCoreNetworkModel Context triple: [3GPP2, usesCoreNetworkModel, IP-based core network]
-
A.
usesCoreNetworkAbbreviation
Indicates that one entity refers to or represents another entity using an abbreviated form specific to a core network context.
-
B.
definesCoreNetwork
Indicates that one entity specifies or establishes the essential or primary network structure for another entity.
-
C.
usedByNetwork
Indicates that something is utilized or operated by a particular network.
-
D.
usesManagementModel
Indicates that one entity applies, follows, or operates according to a particular management model in its management practices or structure.
-
E.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972406a08190bbf355cc7a9f8432 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:04 p.m.