Triple
T25602820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slepian–Wolf coding theorem |
E641830
|
entity |
| Predicate | hasCodingApproach |
P10782
|
FINISHED |
| Object | syndrome-based coding using linear channel codes |
—
|
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: syndrome-based coding using linear channel codes | Statement: [Slepian–Wolf coding theorem, hasCodingApproach, syndrome-based coding using linear channel codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodingApproach Context triple: [Slepian–Wolf coding theorem, hasCodingApproach, syndrome-based coding using linear channel codes]
-
A.
hasApproachType
chosen
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
B.
programmingMethod
Indicates the method, technique, or approach used to carry out a programming-related activity or task.
-
C.
hasApproachStructure
Indicates that one entity possesses or includes an approach structure that provides access or a path leading to another entity.
-
D.
hasProgrammingModel
Indicates that one entity defines, specifies, or is associated with the programming model used or supported by another entity.
-
E.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 21, 2026, 4:36 p.m.