Triple
T24126489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 31.115 |
E597814
|
entity |
| Predicate | usesReferenceSeries |
P59317
|
FINISHED |
| Object | 3GPP TS 31.xxx |
—
|
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: 3GPP TS 31.xxx | Statement: [3GPP TS 31.115, usesReferenceSeries, 3GPP TS 31.xxx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReferenceSeries Context triple: [3GPP TS 31.115, usesReferenceSeries, 3GPP TS 31.xxx]
-
A.
usesSeriesName
Indicates that one entity employs or refers to the series name associated with another entity.
-
B.
usesReferenceObjects
Indicates that an entity performs an action or makes a determination by relying on one or more other entities as reference points or benchmarks.
-
C.
usedInSeries
Indicates that something (such as an element, component, or concept) is employed or appears within a particular series.
-
D.
usesSeriesFormat
chosen
Indicates that one entity presents or organizes its content according to the series format defined or provided by another entity.
-
E.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee9086481909710c6d3291242c3 |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.