Triple
T22951539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 29.512 |
E570032
|
entity |
| Predicate | specificationSeries |
P23871
|
FINISHED |
| Object | 29-series |
—
|
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: 29-series | Statement: [3GPP TS 29.512, specificationSeries, 29-series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specificationSeries Context triple: [3GPP TS 29.512, specificationSeries, 29-series]
-
A.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
B.
designationSeries
chosen
Indicates that one designation belongs to or is part of a broader series of related designations.
-
C.
hasModelSeries
Indicates a relationship where an item or product is associated with a specific model series it belongs to.
-
D.
seriesCode
Indicates that an entity is assigned a specific code identifying the series or collection to which it belongs.
-
E.
currentSeriesIntroduced
Indicates that an entity was first introduced or appeared in the currently ongoing series or installment of a work.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a285448190a718734fe933d51a |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.