Triple
T14457759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDPC |
E358499
|
entity |
| Predicate | usesDecodingAlgorithm |
P14388
|
FINISHED |
| Object | belief propagation |
—
|
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: belief propagation | Statement: [LDPC, usesDecodingAlgorithm, belief propagation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDecodingAlgorithm Context triple: [LDPC, usesDecodingAlgorithm, belief propagation]
-
A.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
B.
decodingMethod
chosen
Indicates the technique or process used to convert encoded or encrypted data back into its original, interpretable form.
-
C.
usesCodec
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
-
D.
usesScrambling
Indicates that one entity applies a scrambling process or technique to another entity or to information associated with it.
-
E.
decryptionRequires
Indicates that performing decryption of some data depends on or needs a specified key, resource, or condition to be fulfilled.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91aabebc819097eb61b2d81c9a91 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.