Triple
T21324445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 29.510 |
E525711
|
entity |
| Predicate | concernsProtocolLayer |
P4644
|
FINISHED |
| Object | application layer |
—
|
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: application layer | Statement: [3GPP TS 29.510, concernsProtocolLayer, application layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsProtocolLayer Context triple: [3GPP TS 29.510, concernsProtocolLayer, application layer]
-
A.
protocolLayer
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
-
B.
concernsLayer
chosen
Indicates that something is related or pertains specifically to a particular layer within a layered structure or system.
-
C.
definesApplicationLayerProtocol
Indicates that an entity specifies or determines which application-layer communication protocol is used by another entity or interaction.
-
D.
securesProtocol
Indicates that one entity protects, safeguards, or enforces the security of a communication or operational protocol for another entity.
-
E.
encryptionProtocol
Indicates that one entity uses, specifies, or is governed by a particular method or standard for encrypting data in its communications or storage.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed652c881909b0db482bc090993 |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:40 p.m.