Triple
T22062151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP Release 5 |
E545179
|
entity |
| Predicate | enhanced |
P39508
|
FINISHED |
| Object | UMTS packet-switched capabilities |
—
|
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: UMTS packet-switched capabilities | Statement: [3GPP Release 5, enhanced, UMTS packet-switched capabilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enhanced Context triple: [3GPP Release 5, enhanced, UMTS packet-switched capabilities]
-
A.
enhancedBy
chosen
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
B.
enhancedSense
Indicates that an entity possesses a heightened or improved sensory ability compared to a normal or baseline level.
-
C.
strengthens
Indicates that one entity increases the power, effectiveness, or resilience of another.
-
D.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
E.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285e8c688190b701e417893cc148 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.