Triple
T22780831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TS 38-series |
E563829
|
entity |
| Predicate | targetTechnologyGeneration |
P9898
|
FINISHED |
| Object | 5G |
—
|
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: 5G | Statement: [TS 38-series, targetTechnologyGeneration, 5G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetTechnologyGeneration Context triple: [TS 38-series, targetTechnologyGeneration, 5G]
-
A.
technologyGeneration
chosen
Indicates the generational level or era of technology associated with or used by an entity in relation to another.
-
B.
targetDeviceGeneration
Indicates the specific hardware or model generation of the device that is the focus or recipient of an action or relationship.
-
C.
technologyLevel
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
D.
targetPlatformGeneration
Indicates the generation or version of the platform that an action, resource, or entity is specifically intended to run on or be compatible with.
-
E.
technologyLevelComparedToPredecessor
Indicates how the technology level of an entity compares to that of its immediate predecessor.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2cab0881908df1d0629b43d350 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:28 p.m.