Triple
T5768055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTLS |
E127260
|
entity |
| Predicate | relationshipToTLS |
P66299
|
FINISHED |
| Object | adapts TLS for unreliable datagram transport |
—
|
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: adapts TLS for unreliable datagram transport | Statement: [DTLS, relationshipToTLS, adapts TLS for unreliable datagram transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToTLS Context triple: [DTLS, relationshipToTLS, adapts TLS for unreliable datagram transport]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
relationshipToState
Indicates a relationship or connection that an entity has with a particular state or governmental body.
-
E.
relationToIETF
Indicates the nature of an entity’s connection or involvement with the Internet Engineering Task Force (IETF), such as affiliation, participation, or oversight.
- F. None of above. chosen
Provenance (4 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02ac9603481909e3fa295d7904a15 |
completed | March 22, 2026, 5:45 p.m. |
Created at: March 22, 2026, 3:49 p.m.