Triple
T14421628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTProto |
E357597
|
entity |
| Predicate | improvedInVersion |
P6555
|
FINISHED |
| Object | MTProto 2.0 addressed weaknesses of MTProto 1.0 |
—
|
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: MTProto 2.0 addressed weaknesses of MTProto 1.0 | Statement: [MTProto, improvedInVersion, MTProto 2.0 addressed weaknesses of MTProto 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvedInVersion Context triple: [MTProto, improvedInVersion, MTProto 2.0 addressed weaknesses of MTProto 1.0]
-
A.
improvesOn
chosen
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
B.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
C.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
D.
introducedInPatch
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
-
E.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91102c3c81908f571a1fff3bdd47 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.