Triple
T24174626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 31.131 |
E599243
|
entity |
| Predicate | usesUnderlyingSpecification |
P5374
|
FINISHED |
| Object | 3GPP TS 31.101 |
—
|
NE NERFINISHED |
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.101 | Statement: [3GPP TS 31.131, usesUnderlyingSpecification, 3GPP TS 31.101]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesUnderlyingSpecification Context triple: [3GPP TS 31.131, usesUnderlyingSpecification, 3GPP TS 31.101]
-
A.
hasSpecification
chosen
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
implementedUnder
Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
-
C.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
D.
extendsSpecificationDefinedIn
Indicates that one specification builds upon, elaborates, or broadens the scope of another previously defined specification.
-
E.
usesSpecEngine
Indicates that one entity employs or relies on a specific engine as its underlying mechanism or processing component.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.