Triple
T14421598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTProto |
E357597
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | MTProto 2.0 |
E357597
|
NE 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: MTProto 2.0 | Statement: [MTProto, hasVersion, MTProto 2.0]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MTProto 2.0 Context triple: [MTProto, hasVersion, MTProto 2.0]
-
A.
MTProto encryption protocol
chosen
MTProto encryption protocol is Telegram’s custom-designed cryptographic protocol that secures user data and message transmission across its messaging platform.
-
B.
Signal protocol Double Ratchet
Signal protocol Double Ratchet is a cryptographic key management algorithm that provides end-to-end encryption with forward secrecy and post-compromise security for secure messaging applications.
-
C.
Signal protocol X3DH
Signal protocol X3DH is a key agreement protocol used in secure messaging systems to establish forward-secure, asynchronous end-to-end encrypted sessions between users.
-
D.
MTK
MTK is the vehicle registration code for the Main-Taunus-Kreis district in the German state of Hesse.
-
E.
MessagePack
MessagePack is a compact, efficient binary serialization format designed to encode structured data for fast transmission and storage across different programming languages.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91102c3c81908f571a1fff3bdd47 |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd648784048190a9c7e95bfeec8b23 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:18 a.m.