Triple
T21192752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NR |
E522250
|
entity |
| Predicate | supportsChannelCoding |
P64030
|
FINISHED |
| Object | LDPC for data channels |
—
|
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: LDPC for data channels | Statement: [NR, supportsChannelCoding, LDPC for data channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChannelCoding Context triple: [NR, supportsChannelCoding, LDPC for data channels]
-
A.
hasChannelCoding
chosen
Indicates that an entity employs a specific channel coding scheme to protect data during transmission over a communication channel.
-
B.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
C.
supportsBlockBasedCoding
Indicates that an entity provides or enables functionality for creating programs using a block-based visual coding interface.
-
D.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
E.
usesCodec
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73338dbe881908360dedad65c964b |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.