Triple
T14421636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTProto |
E357597
|
entity |
| Predicate | usesSerializationFormat |
P77631
|
FINISHED |
| Object | Telegram TL language |
—
|
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: Telegram TL language | Statement: [MTProto, usesSerializationFormat, Telegram TL language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSerializationFormat Context triple: [MTProto, usesSerializationFormat, Telegram TL language]
-
A.
serializationFormatFor
chosen
Indicates the data serialization format used to encode or represent a given resource or entity.
-
B.
hasSerialization
Indicates that one entity is represented, encoded, or stored as a serialized form in another entity.
-
C.
originalSerialization
Indicates that one entity is the initial or source serialized form from which another serialized representation is derived.
-
D.
serializedIn
Indicates that something is published or presented in sequential installments within a larger medium or series.
-
E.
hasSerializationName
Indicates that an entity is associated with a specific name or label used when it is serialized (e.g., in data formats or external representations).
- 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.