Triple
T21224224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 23.272 |
E523049
|
entity |
| Predicate | specifiesInteractionWith |
P143267
|
FINISHED |
| Object | circuit-switched 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: circuit-switched core network | Statement: [3GPP TS 23.272, specifiesInteractionWith, circuit-switched core network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesInteractionWith Context triple: [3GPP TS 23.272, specifiesInteractionWith, circuit-switched core network]
-
A.
appliesToInteraction
Indicates that something (such as a rule, condition, or property) is relevant to or governs a specific interaction between entities.
-
B.
interactionBetween
Indicates a reciprocal or mutual action, influence, or communication occurring between two or more entities.
-
C.
interoperabilityWith
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
D.
usedInteractionType
Indicates the specific type or category of interaction that was used between the related entities.
-
E.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734a9c9f88190817b574f916886e5 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:44 p.m.