Triple
T24157516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TS 52-series |
E598726
|
entity |
| Predicate | includesSpecificationsFor |
P66302
|
FINISHED |
| Object | GSM/EDGE radio network interfaces |
—
|
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: GSM/EDGE radio network interfaces | Statement: [TS 52-series, includesSpecificationsFor, GSM/EDGE radio network interfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSpecificationsFor Context triple: [TS 52-series, includesSpecificationsFor, GSM/EDGE radio network interfaces]
-
A.
hasSpecification
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
extendsSpecificationDefinedIn
Indicates that one specification builds upon, elaborates, or broadens the scope of another previously defined specification.
-
C.
specifiedFor
chosen
Indicates that something is designated or intended to be used for a particular entity, purpose, or context.
-
D.
relatedToSpecification
Indicates that something has a connection or relevance to a particular specification, standard, or set of defined requirements.
-
E.
includesStandard
Indicates that one entity contains, incorporates, or makes use of a particular standard as part of its definition, implementation, or specification.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e5bdb48190aa2d369942b85220 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:31 p.m.